Methods and apparatus for automatically creating multimedia presentations

ABSTRACT

A system and method for communicating a multimedia presentation between a presenter and an audience is described. Services provided via a network facilitate the communication, and include real-time determination of remaining portions of a presentation responsive to “on the fly” presentation modifications, automated filtering and prioritization of audience feedback to a presenter, and integration with one or more customer data resources.

FIELD OF THE INVENTION

The present disclosure relates generally to multimedia presentations,and more particularly to methods and systems for controllingpresentation content, and facilitating audience participation.Augmenting a presentation with information from a third party resource,e.g., multimedia content, and a customer data resource, e.g., CRM, andreal-time capture of information from an audience to, e.g., CRM or athird party resource, may further enhance the audience's experienceduring and after a multimedia presentation.

BACKGROUND

A live media presentation is an event at which a speaker—thepresenter—uses speech and a display to inform, persuade, or build goodwill to attendant audience members located within view of the display.Live media presentations co-locate the presenter, display, and audiencemembers, commonly in meeting rooms, conference halls, and classrooms.

Typically in presentations a presenter uses support services (e.g.,presentation aids, tools for audience interaction) to enhancepresentations. A simple example of a presentation aid is a pointer todirect audience attention to a particular location within thepresentation. Such pointers traditionally have been dedicated peripheraldevices to interact with the display, e.g., a telescoping pointer rod,an electronic mouse, and a laser pointer. Audience feedback is typicallysought by the presenter using verbal interaction, but may also beunsolicited and include comments and general information. In addition,electronic systems provide a way for audience members to providefeedback via personal devices by communicating, e.g., over a network,back to the presenter, who is connected to the network via a device. Thepresenter may also send feedback requests to the personal devices of theaudience over the network.

Presenting a multimedia presentation to an audience neverthelesspresents real-time logistical challenges to the presenter. For example,interacting with an audience and entertaining feedback, e.g., questionsand comments, inevitably affects presentation pacing and timing and, inthe absence of effective moderation, can also be distracting to thepresenter. Moreover, deviation from a rehearsed presentation may imperilthe timing, flow, and integrity of the actual presentation—adisincentive to interact with an audience, thereby potentially stiflingcommunication.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter presented herein is illustrated by way of example,and not by way of limitation, in the figures of the accompanyingdrawings and in which like reference numerals refer to similar elementsand in which:

FIG. 1 depicts a computer-implemented system for presenting a multimediapresentation in accordance with one embodiment;

FIG. 2 is a flowchart depicting a method for presenting a multimediapresentation in accordance with one embodiment;

FIG. 3 is a flowchart depicting a method for presenting a multimediapresentation in accordance with another embodiment;

FIG. 4 depicts portions of a presentation and data tables relating to amultimedia presentation in accordance with one embodiment;

FIG. 5 is a flowchart depicting a method for estimating a duration of aportion of a multimedia presentation in accordance with one embodiment;

FIG. 6 is a flowchart depicting a method for automating feedbackmoderation relating to a multimedia presentation in accordance with oneembodiment;

FIG. 7A depicts multi-layered slides relating to a multimediapresentation in accordance with one embodiment;

FIG. 7B depicts portions of a presentation and data tables relating toannotating a multimedia presentation in accordance with one embodiment;

FIG. 7C sets forth flowcharts depicting methods for annotating amultimedia presentation in accordance with one embodiment;

FIG. 8 depicts presentation tools in accordance with one embodiment;

FIG. 9 depicts a view of a user interface on a client device inaccordance with one embodiment;

FIG. 10 depicts a view of a user interface on a client device inaccordance with another embodiment;

FIG. 11 depicts a view of a data structure for managing a masterconference in accordance with one embodiment; and

FIG. 12 depicts a prior art suitable computing environment in which theinvention may be implemented.

DETAILED DESCRIPTION

FIG. 1 depicts a computer-implemented system 100 for preparing anddelivering a multimedia presentation in accordance with one embodiment.The presentation is delivered by a presenter 155 to an audience, e.g.,members 115, 125, and 135 in a room 101 of a building, who view thepresentation on a conventional display device 162, and on conventionalwireless handheld devices 110, 120, and 130. In one embodiment, displaydevice 162 is a wireless handheld device, e.g., similar to or the sameas devices 110, 120, and 130. The presentation may include one or moreportions, e.g., slides, video, and audio segments, arranged to achieve adesired pacing and flow. Each portion of the multimedia presentation mayinclude a group of one or more slides. A remote server, e.g.,presentation server 165 and data server 185 in one embodiment, includespresentation services 175, 178, 180, and 183, customer data service 194,which in some embodiments supports the presentation services, andstorage, e.g., computer disks and databases, for creating, storing,rehearsing, and displaying the presentation. In one embodiment, customerdata service 194, also referred to as a customer data resource, may be acustomer relationship management system (“CRM”). In another embodiment,customer data service 194 may be a simple address book, a contactsdatabase, or an application. In still another embodiment, customer dataservice 194 serves as a gateway for third party and other resources,e.g., resources provided by Zoho Corporation Pvt. Ltd., Chennai, India,and Zoho Corporation, Pleasanton, Calif., including without limitation,CRM, Sales IQ, Campaigns, Survey, Sites, Social, Contact Manager, Mail,Docs, Projects, Connect, Bug Tracker, Meeting, Vault, Showtime, Support,Assist, Books, Invoice, Subscriptions, Expense, Inventory, Recruit,People, Reports, and Creator, and, e.g., a third party CRM system. Aswill be seen, system 100 also gives the presenter real-time informationrelating to audience members, assists the presenter in makingpresentation changes during a presentation to, e.g., respond to audiencefeedback, e.g., Q&A, and rearrange the order and duration ofpresentation portions (informed by presentation history and customerdata, e.g., customer relationship management “CRM” data). Customer datainclude “lead scoring” results in one embodiment, described in moredetail below. System 100 adjusts the respective durations ofpresentation portions responsive to presentation changes to, e.g.,maintain an overall presentation duration budget, and helps to avoidpresenter “information overload” by automatically moderating audiencefeedback to the presenter.

System 100 also advantageously enables the presenter to, e.g., respondimpromptu to topics relevant to an audience, and to rearrange thepresentation as desired “on the fly” while preserving the pacing,duration, and integrity of the presentation as a whole. Moreover,metrics and other data relating to the presentation are saved forapplication to future preparations and presentations, thereby providingfor continuous process improvement. For example, a particularly favoredportion, e.g., one that is entertaining, informative, or tending toinduce product interest, may be identified as such. System 100 enablesidentifying (“flagging” or “tagging”) the favored portion in real-time.Identification may be performed manually, e.g., during the presentation,via e.g., an on-screen icon appearing on wireless handheld presenterdevices 150 and 160. Identification may also be performed automatically,e.g., via heuristics analysis provided by presenter support service 178.Heuristics include correlating audience feedback, e.g., Q&A and commentswith, e.g., CRM data and presentation portions to identify particularlyfavored portions. Applying heuristics advantageously identifiespotentially important audience member interests after a presentation—ineffect performing a forensics analysis on the proceedings—therebyproviding powerful sales and marketing information to an organization.Audience service 178 captures audience feedback, e.g., textually asentered by a presenter or a moderator, or by, e.g., converting arecording of the presentation proceedings to a transcript. Similarly, aportion precipitating audience feedback indicating its message is, e.g.,boring or unclear, may be identified for improvement. Similarly,follow-up and “to-do” items precipitated by audience feedback,including, e.g., product questions and sales leads, may be saved tocustomer (CRM) data, thereby enhancing an organization's sales andmarketing processes.

Returning to FIG. 1, a display device 162, e.g., a presentation devicesuch as a large flat screen television, a projection device, or awireless handheld device, communicates with the remote server via anetwork, which may be a private network or a public network. As depictedin FIG. 1, display device 162 communicates with the remote server viapublic WAN 108, e.g., a public network such as the Internet, or a VPNtunnel over the Internet, and projects the multimedia presentation tothe audience. Display 162 accesses public WAN 108 via a local areanetwork, LAN 107, which may be wired or wireless as one of skill in theart would readily appreciate, or via a cellular network, e.g., cell 106.In another embodiment, a presentation interface for the multimediapresentation is provided to presentation device 162 via the network. Awireless handheld presenter device 150, e.g., an iPhone or iPad providedby Apple, Inc. of Cupertino, Calif., including, e.g., devices 810 and860 depicted in FIG. 8, devices 950 and 1050 respectively depicted inFIGS. 9 and 10, and a wireless handheld device 160, e.g., a laptopcomputer provided by Dell, Inc. of Round Rock, Tex., also communicatewith the remote server via public WAN 108. The devices access public WAN108 via LAN 107 or a cellular network, e.g., cell 106. Other wirelesshandheld devices, e.g., iPhone or iPad, in room 101, include wirelesshandheld audience devices 110, 120, and 130, used respectively byaudience members 115, 125, and 135, and wireless handheld moderatordevice 140 used by moderator 145. As with wireless device 150, thesedevices similarly communicate with the remote server via public WAN 108,LAN 107, cell 106, or via another cellular network, cell 105.

In the embodiment depicted in FIG. 1, the remote server includespresentation server 165 and data server 185. The remote server,sometimes referred to as an “application server,” is typically “cloudbased,” that is, it is not co-located at the site of a presentation,e.g., room 101. It may be implemented in a distributed fashion, orco-located, as warranted by circumstances. Components depicted inservers 165 and 185 may alternatively be situated within a single serverin another embodiment, or may be realized as individual servers, eachproviding one or more services in yet another embodiment. As depicted inFIG. 1, servers 165 and 185 include respectively memory 170 and 190,processor 173 and 193, and storage 184 and 195. A non-transitorycomputer-readable medium, e.g., memories 170 and 190, holds instructionsfor execution by a processor, e.g., processors 170 and 190. Theinstructions provide various interfaces for a multimedia presentation tovarious devices, e.g., a display device, and wireless handheld devices,via a network, as described below. The processors, memory, and storagemay be realized within a single hardware server. Alternatively a servermay be virtualized, e.g., VMWARE, and VIRTUALBOX, or distributed acrossvarious locations, e.g., “in the cloud,” and intercommunicating with oneanother via a network.

Services 175, 178, 180, 183, and 194 included in the remote serverfacilitate creating and delivering multimedia presentations, includingcreating, rehearsing, adapting, rearranging, and viewing portions of amultimedia presentation. The services may also variously provideinterfaces for various wireless handheld and other display devices viathe network, such as flow control commands, viewing commands, updatingcommands, and synchronization commands. Presentation services alsoinclude associating customer data, including audience member feedback,with one or more portions of a multimedia presentation, and servicesrelating to receiving and moderating feedback to presenter 155 fromaudience members, e.g., members 115, 125, and 135. Services typicallyintercommunicate via application programming interfaces (“API”), and mayalso communicate through other services, and communicate with variousdevices, e.g., desktop computers, laptop computers, and wirelesshandheld devices, via public WAN 108, and via local area networks, e.g.,LAN 107. A service supporting a user interface, e.g., a mobileapplication or web client, may communicate with the client over anetwork. In general, software modules or applications may communicatewith each other to exchange information or data. For example,information may be exchanged between software modules or applicationsusing webhooks or API calls. When an update, change, or event occurs inan application, the application may provide via a webhook to otherapplications, e.g., delivered at a URL, one or more triggers, data, orchanges to data, and information related to events or data changes. AnAPI call may be made from one application to another to obtain datachanges periodically, or on demand, e.g., triggered by a user to updatecustomer data. In one embodiment, functions provided by individualservices identified in FIG. 1 may be arbitrarily implemented andprovided via a plurality of inter-communicating services. Functionsprovided by services identified in FIG. 1 may be implemented andprovided by a single service in accordance with another embodiment. Inanother embodiment, one or more of services 175, 178, 180, 183, and 194,communicate with one or more systems, e.g., an in-house or outsourcedcustomer relationship management (“CRM”) system, and e.g., transmit andreceive CRM data. For example, an outsourced CRM system communicates anotice, e.g., via a webhook, wherein the webhook provides updated orchanged data upon the occurrence of any updated or changed data, todocument management service 175 and audience support service 180, thatits CRM data has changed. In response, audience support service 180transmits an icon to the screen of wireless handheld presenter device150 to alert presenter 155 of the change. Presenter 155 may activate theicon to view the CRM data on device 150. In another embodiment,activating the icon transmits the CRM data, for example a data sheetrelating to a product of interest to an audience member who may be apotential customer, to presentation device 162, thereby including it inthe presentation “on the fly.” Document management service 175 respondsto the change in another embodiment, communicates with the third partyCRM to obtain the CRM data, and transmits the CRM data to the screen ofa device in communication with document management service 175, e.g.,device 160.

Document management service 175 provides a user interface for creating,modifying, and maintaining a multimedia presentation. In one embodiment,document management service 175 provides a presentation interface forthe multimedia presentation to a presentation device, e.g., displaydevice 162, via the network. In another embodiment, service 175 providesa presenter interface for the multimedia presentation to a wirelesshandheld presenter device, e.g., devices 150, 160, 810, and 860, via thenetwork. A presentation may include audio, video, and slides, such asslides 401-410, and slides 701-710, depicted respectively in FIGS. 4 and7. In one embodiment, the user interface is web-based, e.g., HTML istransmitted to a web browser; in another embodiment, the user interfaceis provided in a mobile application for execution on, e.g., Android,iOS, and Windows-based mobile devices. Document management service 175maintains a data structure as depicted in FIG. 4 in one embodiment,associating a multimedia presentation with events and metrics relatingto the presentation, e.g., portion durations, audience feedback,including historical data, e.g., events, metrics, and analytics.

Presenter support service 178 supports the presenter during apresentation. In one embodiment, presenter support service 178 providesa presentation interface for the multimedia presentation to thepresentation device, e.g., display device 162, via the network. Inanother embodiment, service 178 provides a presenter interface for themultimedia presentation to a handheld wireless presenter device, e.g.,devices 150, 160, 810, and 860, via the network. Through service 178,presenter 155 controls the movement and flow of the presentation,typically via a wireless handheld presenter device 150 running, e.g., abrowser or application, thereby enabling presenter 155 to move aboutfreely. Presenter 155 controls the movement and flow of the presentatione.g., via flow control commands, by selecting one or more portions torender to the display device 162, and to display to wireless handheldaudience devices 110, 120, and 130. The presentation may be synchronizedacross devices, e.g., the same portion is displayed on each, or thepresentation may be individualized such that each member, e.g., 115,125, 135, views different portions of the presentation. Service 178, inconjunction with audience presentation service 180, enables presenter155 to select a range of portions, e.g., slides, to deliver to wirelesshandheld audience devices 110, 120, and 130. For example, presenter 155may determine, after reaching portion no. 10, to allow members 115, 125,and 135 to access, e.g., scroll through and view portions alreadypresented, e.g., portions 1-9. Service 178 communicates the rangethrough an API to document management service 175, which in turncommunicates through an API to audience support service 180 (describedmore fully below). Presenter support service 178 and audience supportservice 180 communicate directly with one another in another embodiment.Service 180 thereafter delivers, or makes accessible, portions of themultimedia presentation already presented by the presenter to audiencemembers, but not portions not yet presented.

An advantageous aspect of presenter support service 178 is aninteractive electronic pointer. Presenter 155 communicates with audiencemembers 115, 125, and 135 in a variety of ways. The presenter 155 maycommunicate verbally, or by displaying portions of the presentation on,e.g., devices 110, 120, and 130, display device 162, or by “pointing to”items on-screen, in the presentation itself. In one embodiment,presentation service 178 places an interactive electronic pointer withinthe presentation. In another embodiment, presentation service 178enables the presenter to activate and place the interactive electronicpointer by, e.g., selecting an icon provided as a pointer, or by, e.g.,tapping-and-holding on the screen of device 150. Display device 162shows a pointer 163 situated above the second bar of an on-screen barchart. Moving to a previous or subsequent presentation portion refreshesor resets the pointer. Wireless audience display device 120 shows thesame bar chart seen on device 162, and includes pointer 121 synchronizedto approximately the same relative location as pointer 163. So too forpointer 151 appearing on wireless handheld presenter device 150, andpointer 161 appearing on laptop 160. In another aspect, annotation andother tools enable presenter 155 to further communicate with an audienceas described more fully with respect to FIG. 8 below.

In one embodiment, pointer 151 appears at a location. Pointer 151 isinitiated by the presenter in another embodiment. On wireless handhelddevice 150, presenter 155 swipes pointer 151, causing it to move to anew pointer location. The application, or, e.g., a web client ofpresenter service 178, running on device 150, determines an updatedposition corresponding to the new pointer location, and transmits theupdated position to presentation service 178. Service 178 in turncommunicates the updated position via, e.g., an API, to audience supportservice 180, which synchronizes pointers 121, 161, and 163 respectivelyon handheld devices 120, 160, and display device 162, thereby reflectingthe new pointer location. In another embodiment, presenter supportservice 178 additionally communicates the updated position to documentmanagement service 175 to synchronize the pointer corresponding to oneor more devices communicating with document management service 175,e.g., pointers 161 and 163 respectively, of devices 160 and 162. Inanother embodiment, presenter 155 re-orients device 150 by, e.g., movingit about in space. The application running on device 150 reads positionand accelerometer information from sensors in device 150, determines anupdated pointer position, and communicates it to presentation server178. As before, server 178 communicates the updated position to audienceservice 180, which in turn causes the wireless handheld devices in room101, e.g., devices 110, 120, 130, 140, 150, 160, and display device 162,to reflect their respective new pointer locations. In anotherembodiment, server 178 also communicates the updated position todocument management service 175, in turn causing devices incommunication with document management service 175, e.g., wirelesshandheld device 160 and display device 162, to reflect their respectivenew pointer positions.

In another embodiment, audience support service 180 and presenterservice 178 enable roaming among multiple simultaneous multimediapresentations. In a venue in which multiple multimedia presentations arebeing presented, an audience member may wish to sample more than onepresentation, roaming among presentations as desired. Audience supportservice 180 receives location-related information from one or morewireless handheld devices, e.g., devices 110, 120, 130, 140, 150, and160. Location-related information may be derived from, e.g., Wi-Fi orcellular triangulation, near-field communications, geo-fencing, globalpositioning services, and Bluetooth beacons. FIG. 1 depicts Bluetoothbeacons 111, 112, and 113 near the perimeter of room 101 in FIG. 1 todetect movement of one or more wireless handheld devices.

Presenter service 178 maintains a real-time association between eachmultimedia presentation currently being presented and its location,e.g., first, second, and third presentations are respectively beingpresented in first, second, and third rooms. Presenter service 178obtains location-related information for a multimedia presentation,e.g., the first presentation, from a wireless handheld device, e.g.,presenter devices 150 and 160, moderator device 140 (including via,e.g., moderator service 183), display device 162, or any deviceassociated with a presentation, and associates the location-relatedinformation to the multimedia presentation, e.g., the firstpresentation, in accordance with one embodiment. Document managementservice 175 receives location-related information corresponding topresenters and audience members from other services, e.g., services 178,180, and 183 in accordance with one embodiment, and maintains andassociates the location-related information with presentations andaudience members. Audience support service 180 receives location-relatedinformation from a first wireless handheld device situated in the firstroom and communicates the location-related information to presenterservice 178. Audience support service 180 communicates thelocation-related information to document service 175 in accordance withone embodiment. Moderator support service 183 receives location-relatedinformation from a first wireless moderator device, e.g., device 140,and communicates the location-related information to document service175 in accordance with another embodiment. Service 178 identifies thatthe first wireless handheld device is in the first room, and requests,through an API to document management service 175, for it to retrievethe first multimedia presentation. Service 175 then communicates throughan API to audience support service 180 which begins transmitting aportion of a first electronic presentation to the first wirelesshandheld device comprising a portion of the first multimediapresentation, including any portion already presented by the presenterto audience members and real-time portions of the presentation, to thefirst wireless handheld device. The first electronic presentationincludes first visual and aural components corresponding to the firstmultimedia presentation. In general, an electronic presentation, e.g.,the first electronic presentation, may comprise one or more auralcomponents, one or more visual components, or one or more aural andvisual components.

Presenter support service 178 performs functions as described below.Service 178 identifies the audience member corresponding to the firstwireless handheld device in one embodiment, and alerts presenter 155.Presenter support service 178 communicates via an API with customer dataservice 194 in another embodiment, to e.g., a CRM system, to associateinformation relating to the audience member's consumption of the firstmultimedia presentation, including, e.g., portions viewed, and durationsof viewing. As the audience member roams, e.g., from the first to thesecond multimedia presentation, audience support service 180 receivesupdated location-related information from the first wireless handhelddevice, and communicates the updated information to presenter supportservice 178, which alerts presenter 155 that the audience membercorresponding to the first wireless handheld device has left the firstmultimedia presentation. In another embodiment, presenter supportservice 178 communicates with customer data service 194, e.g., to updateCRM data relating to the audience member including information relatingto the audience member's viewing of the first multimedia presentation.

Once the first wireless handheld device enters the second multimediapresentation, audience support service 180 transmits updatedlocation-related data to presenter support service 178, which identifiesthat the first wireless handheld device is in the second room. Asdescribed with respect to the first multimedia presentation, presentersupport service 178 alerts a second presenter that the audience memberhas arrived, audience support service 180 begins transmitting a portionof a second electronic presentation comprising a portion of the secondmultimedia presentation to the first wireless handheld device, and CRMdata is updated. The second electronic presentation includes secondvisual and aural components corresponding to the second multimediapresentation. An audience member may therefore conveniently roam amongpresentations and automatically receive, on his or her wireless handhelddevice, the appropriate presentation. Moreover, audience member roamingdata captured, e.g., in a CRM system, enables analysis, e.g., relatingto the efficacy of a multimedia presentation and audience memberpreferences. Document support service 175 performs the functionsdescribed above with respect to presenter service 178 in accordance withanother embodiment. Audience support service 180 routes the first visualcomponent to, e.g., window 917 of wireless handheld audience device 950,as depicted in FIG. 9, and the second visual component to window 935, ina “picture-in-picture” (“PIP”) viewing mode, in accordance with anotherembodiment. In this mode, the first and second visual components overlapone another. The first and second visual components are respectivelydisplayed side by side in windows 1017 and 1035 on wireless handhelddevice 1050 as depicted in FIG. 10, in a “picture outside of picture”(“POP”) viewing mode, in accordance with still another embodiment. Aswireless handheld devices roam (see below), audience support service 180receives location information from the devices and in response, maytranspose (swap) the first and second visual components respectivelybetween windows, e.g., between windows 917 and 935, and between windows1017 and 1035. Audience service 180 receives an express preference froma wireless handheld audience device, e.g., devices 110, 120, or 130, inaccordance with another embodiment, and in response, may transpose(swap) the first and second visual components respectively betweenwindows, e.g., between windows 917 and 935, and between windows 1017 and1035.

In another aspect, the first electronic presentation may include thefirst visual component corresponding to the first multimediapresentation and the second aural component corresponding to the secondmultimedia presentation. An audience member may therefore advantageouslyconsume two multimedia presentations simultaneously, here, the firstmultimedia presentation visually and the second multimedia presentationaurally. Similarly, the second electronic presentation may include thesecond visual component corresponding to the second multimediapresentation and the first aural component corresponding to the firstmultimedia presentation. Audience support service 180 receives anexpress selection from a wireless handheld audience device, e.g., 110,120, and 130, associating visual and aural components to an electronicpresentation in accordance with one embodiment. Audience support service180 maintains associations among an arbitrary number of electronicpresentations, and an arbitrary number of visual and aural componentscorresponding to multimedia presentations. For example, when the firstwireless handheld device roams, e.g., from the first room to the secondroom and audience support service 180 transmits the second electronicpresentation to the first wireless handheld device, the secondelectronic presentation may include the second visual component and thefirst aural component. Audience service 180 selects an aural componentto transmit to a wireless handheld audience device based onlocation-related information it receives from the device in oneembodiment. In another embodiment, audience service 180 selects theaural component in response to an express selection it receives from thewireless handheld device, the selection asserted by an audience member.

Audience support service 180 supports communication with wirelesshandheld audience devices, e.g., devices 110, 120, and 130, includingdelivering the presentation to the wireless handheld audience devices,enabling viewing by audience members, e.g., 115, 125, and 135, ofportions of a presentation, sending information to audience members, andreceiving and responding to audience feedback. In one embodiment,audience support service 180 provides an audience interface for themultimedia presentation to a wireless handheld audience device, e.g.,devices 110, 120, and 130, via the network. Information sent to anaudience member includes, e.g., poll questions, and a profile ofpresenter 155. Audience feedback includes, e.g., “likes,” questions, andcomments, and may be formatted as text, audio, or video content. Aninterface, e.g., provided by audience support service 180, for use byaudience members 115, 125, and 135, is provided by an applicationexecuting respectively on devices 110, 120, and 130 in one embodiment. Aweb browser-based interface, e.g., provided by audience support service180, is provided in another embodiment. As described above, presentersupport service 178 (and in accordance with another embodiment, documentmanagement service 175) provides electronic pointer synchronizationacross devices including wireless handheld audience devices. In oneembodiment, an audience member, e.g., 115, 125, and 135, “logs in”respectively on wireless handheld audience device 110, 120, and 130,e.g., upon entering the building or room 101. In one embodiment,audience support service 180 identifies the member, and via, e.g., anAPI, communicates directly or via document management service 175, tocustomer data service 194 to associate the member with a customer datarecord, and further communicates with presenter support service 178directly, or via document management service 175, to alert the presenterto the presence of the audience member. In another embodiment, presentersupport service 178 records that the audience member is present, inpreparation for a query from presenter 155.

Automated moderator service 183 supports presenter 155 by serving tomoderate a flow of audience feedback to the presenter. In oneembodiment, service 183 provides a moderator interface for themultimedia presentation to a wireless handheld moderator device, e.g.,device 140, via the network. Service 183 filters and conditionally sendsthe feedback to the presenter in one embodiment. In another embodiment,presenter support service 178 receives audience feedback via, e.g., anAPI from audience support service 180, and displays the feedback onwireless handheld moderator device 140 for viewing by a moderator 145.The moderator then determines whether to forward the audience feedbackto the presenter. In another embodiment, automated moderator service 183operates automatically, in lieu of a human moderator. Factors thatautomated moderator service 183 “considers” include whether an audiencemember is a “hot” sales prospect, that is, one having a pending salesmatter of significance, or whether a particular item of feedback, e.g.,an insightful question or comment, relates to the subject matter of thepresentation. By performing machine-based analysis, e.g., associatingand cross-correlating inputs retrieved from other services, with one ormore portions of the presentation and the audience feedback itself,automated moderator service 183 filters the feedback—dropping somealtogether—while prioritizing the rest, and provides it to the presenterwith the objective of enhancing e.g., a pending sales matter, or thepresentation as a whole. In another embodiment, simple weighting andrules are applied to prioritize and present audience feedback to thepresenter. In one embodiment, the audience feedback, e.g., after theassociating and cross-correlating, or, e.g., at any time, is directed tocustomer data service 194 for storage, e.g., in an appropriate CRMcategory, e.g., customer data.

In one embodiment, automated moderator service 183 is configured toreceive audience feedback via, e.g., an API from audience supportservice 180. Automated moderator service also communicates via, e.g.,APIs, with document management service 175, presenter support service178, audience support service 180, and customer data service 194.Automated moderator service 183 retrieves current and historical data,e.g., duration and related data for the presentation, customer data, andreceives the identity of the portion of the presentation currently beingdisplayed. Service 183 retrieves customer data, e.g., CRM data, linkedto the presentation data, from customer data service 194. Automatedmoderator service 183 also retrieves customer data directly fromcustomer data service 194 relating to audience members, e.g., members115, 125, and 135, who were previously identified as present. Fromaudience support service 180, automated moderator service 183 receivesaudience feedback.

FIG. 2 is a flowchart 200 depicting a method for presenting a multimediapresentation in accordance with one embodiment. The method facilitatescommunication between a presenter of a multimedia presentation andaudience members of the presentation co-located with the presenter in aroom of a building. At step 205, the method provides a presentationinterface for a multimedia presentation device, e.g., presentationdevice 162, via the network. In another embodiment, presentation device162, e.g., a large flat screen display or a projection device, situatedin room 101 of a building, communicates via a public network, e.g.,public WAN 108, with a remote server, e.g., presentation server 165 anddata server 185, for presenting the multimedia presentation to membersof an audience. The remote server includes processors, memory, storage,e.g., hard disk and database storage, and services that receivecommands, intercommunicate with one another, and deliver portions of themultimedia presentation and other data to various devices in room 101.The remote server stores one or more multimedia presentations, typicallyassociated with one or more user accounts, data relating to thepresentations, including historical data, e.g., metrics and analyticsrelating to, e.g., durations of portions of multimedia presentations,audience feedback, e.g., “likes” and comments, and presenter comments.

In step 210, a presenter interface for the multimedia presentation isprovided to a wireless handheld presenter device, e.g., handheld 150 andlaptop 160, via the network. The wireless handheld presenter device,e.g., handheld 150 and laptop 160, communicates in another embodimentwith the remote server via the public network, e.g., public WAN 108. Instep 215, the method sends a portion of the multimedia presentation tothe wireless handheld presenter device, e.g., device 150, via thenetwork. In another embodiment, a presenter 155 operates the handheldpresenter device in another embodiment, which issues commands to theremote server. In response to the commands, the remote server sends, instep 215, a portion of the multimedia presentation to the presenter, whomay view it on wireless handheld presenter device 150. In step 220, themethod sends a portion of the multimedia presentation to thepresentation device, e.g., presentation display 162, via the network.The portion of the multimedia presentation is also sent to wirelesshandheld audience devices, e.g., 110, 120, and 130 in anotherembodiment, via the network. In still another embodiment, the remoteserver sends the portion of the multimedia presentation to thepresentation device 162, and to wireless handheld audience devices,e.g., devices 110, 120, and 130. The remote server may send differentportions to presentation device 162, and to each handheld presenterdevice, and may render the portion appropriately for the respectivedisplay device. For example rendering a portion to a handheld device mayrequire fewer elements, arranged and scaled differently than the sameportion rendered to presentation device 162. A portion may include oneor more audio and video elements, e.g., live streams or files, links tostreams or files, and text. A presentation may be created inpresentation software, e.g., Zoho Presentation provided by ZohoCorporation Private Limited, and Microsoft PowerPoint. In anotherembodiment (not depicted in FIG. 2), display device 162, and handhelddevices 110, 120, and 130, project the portion of the multimediapresentation to audience members within the room.

In step 225, the method estimates and displays to the wireless handheldpresenter device, e.g., device 150, a duration corresponding to themultimedia presentation and the portion of the multimedia presentation.In another embodiment, presenter support service 178 estimates aduration for the portion of the multimedia presentation being displayed,and displays it to presenter 155 on the wireless handheld presenterdevice 150. Support service 178 also estimates a duration correspondingto the multimedia presentation as a whole, and also displays it to thepresenter. The estimates may also be displayed on wireless handheldmoderator device 140 for viewing by moderator 145. In step 230, themethod receives commands from the wireless handheld presenter device,e.g., device 150, via the network. In another embodiment, wirelesshandheld presenter device 150 next sends commands to the remote servervia public WAN 108, and in response, the remote server updates theportion of the multimedia presentation projected on display device 162,and displayed on handheld devices, e.g., 110, 120, and 130, within room101. In step 235, the method updates the portion of the multimediapresentation via the network. The method finishes at step 295.

Wireless handheld audience devices 110, 120, and 130, e.g., an iPhone oriPad provided by Apple, Inc. of Cupertino, California, include, in oneembodiment, an application enabling the devices to communicate with theremote server and receive commands from it to, e.g., appropriatelyscale, arrange, and display a portion of the multimedia presentation.Accordingly, updating the multimedia presentation to these devices,e.g., presentation hardware, comprises the remote server sending secondcommands to the presentation device. Display device 162 may similarlyinclude application software capable of receiving commands from theremote server. In addition to the remote server updating the portion ofthe multimedia display in response to commands from device 150, theremote server also sends a second portion to the audience devices, e.g.,110, 120, and 130, after sending the portion first-mentioned.Alternatively, the remote server may arrange the portions such that thesecond portion precedes the first-mentioned portion in the presentation.

FIG. 3 is a flowchart 300 depicting a method for presenting a multimediapresentation in accordance with another embodiment. FIGS. 2 and 3 sharesimilar elements. For brevity, elements of FIG. 3 corresponding toelements of FIG. 2 that have been described above, are omitted from thedescription that follows. At step 340, the method provides an audienceinterface for the multimedia presentation to a wireless handheldaudience device, e.g., devices 110, 120, and 130, via the network, andin step 345, identifies the audience member, e.g., 115, 125, and 135,corresponding to the wireless handheld audience device. In step 350, themethod retrieves, via the network, customer data corresponding to theaudience member. Customer data may be retrieved from any number ofresources, e.g., a CRM system, a contacts database, or an address book,any of which may be “in the cloud” resources, hosted in-house,outsourced. Presenter service 178 directly performs the retrieval inaccordance with one embodiment. In another embodiment, presenter service178 makes its request via customer data service 194. In anotherembodiment, after communicating between a wireless handheld device andthe remote server via a public network, e.g., public WAN 108, the methodidentifies the audience member, e.g., 115, 125, and 135, correspondingto the wireless handheld audience device, respectively 110, 120, and130. “Connecting” includes establishing communication between or amongone or more network nodes, e.g., a remote server, including any service175, 178, 180, 183, or 194, which may receive communication from adevice, e.g., display device 162, and wireless handheld presenterdevices 150 and 160, and thereafter establish a connection via, e.g.,TCP/IP. In another embodiment, communication between a device and aremote server is established via, e.g., a manual or automatic logonprocess. A remote server may similarly initiate and establishcommunication with a device. Audience support service 180 communicateswith an application running on the handheld device (110, 120, and 130)to retrieve an identification handle corresponding to the audiencemember, then, via, e.g., an API, it communicates in step 350 to customerdata service 194 to retrieve customer data corresponding to thecustomer. Customer data includes the name of each audience memberidentified, and may also include information relating to, e.g., pendingsales matters. Audience support service 180 next communicates via API topresenter service 178, which in turn communicates to an applicationrunning on wireless handheld presenter device 150 to display topresenter 155 the customer information relating to audience members 115,125, and 135, identifying them as, e.g., current or prospectivecustomers. The method finishes at step 395.

FIG. 4 depicts portions of a presentation and a data structure 400relating to a multimedia presentation in accordance with one embodiment.For a multimedia presentation to be successful, a presenter needs toguide an audience through the presentation, keep their interest, andattract their attention. One aspect of keeping interest is managingduration—the time spent on any portion and the presentation as a whole.For example, if audience feedback includes an insightful question orcomment, the audience may welcome an extended colloquy. Or, if a “hot”sales prospect joins an audience, the presenter may wish to modify thepresentation responsive to the feedback, and spend more time on a topicof relevance to that prospect. In response, the presenter may modify theduration, order, or flow of a presentation. Modifying the presentationmay also comprise increasing the audio volume of the presentation. Inturn, however, the duration of portions remaining in the presentation,and a multimedia presentation duration, e.g., a duration of thepresentation as a whole, should be determined to avoid running too long,or “losing” the audience.

During and after creation, a presentation is typically rehearsed, andits portions are ordered, reordered, and modified appropriately. Apresenter may wish to time her talk, view a slide with notes, performon-the-spot edits, and “shuffle the deck” to sharpen memory and recallof the presentation. Rehearsal may be accomplished in a presentationenvironment, e.g., including display device 162, wireless handheldaudience devices, e.g., 110-130, and wireless handheld presenter device150. Rehearsal may be undertaken in any location, e.g., remotely,“on-the-go,” via a mobile application, also referred to as a Trainerapplication, in accordance with another embodiment. Durations relatingto each portion are saved in a data structure 400 depicted in FIG. 4. Apresentation metadata service 490 manages aspects of metadata relatingto multimedia presentations. Here, a presentation comprising portions401-410 is depicted in FIG. 4. Tables 420-450 comprise metadata relatingto the presentation. For convenience, FIG. 4 depicts four tables(420-450), however, fewer or more may be used within the scope of theinvention. As depicted, each row of tables 420-450 corresponds to aportion of the presentation, e.g., row 1 to portion 401, row 2 toportion 402, and so forth. Tables 440 and above, and corresponding table480 and above, include historical data from prior runs-through of apresentation. Table 430 and corresponding table 470 include datacollected during a current run-through of a presentation. At theconclusion of a rehearsal, or a presentation to an audience,presentation metadata service 490, communicating via, e.g., an API withpresenter support service 178, receives from service 178, a durationcorresponding to each portion of the presentation determined duringrehearsal, and records it in the “Dur” (duration) column respectively inrows of table 430. In one embodiment, customer data are also stored to,e.g., a CRM database, and one or more links to one or more customer datarecords relating to, e.g., one or more audience members, are stored inthe “CD” column of table 430. At the conclusion of a rehearsal oraudience presentation, table 430 and related table 470 are renumberedand respectively grouped with historical tables 440, 450, and 480.Metadata relating to any presentation therefore become available ashistorical data for future presentations, thereby enabling processimprovements to be made. At the beginning of a new rehearsal or audiencepresentation, “new” tables 430 and 470 are created for capturing newpresentation metadata.

In one embodiment, presentation metadata service 490 may be incorporatedin, or distributed among, any of document management service 175,presenter support service 178, and audience support service 180. Aweighting factor corresponding to each portion is recorded in a columnlabeled “Wt,” depicted adjacent to the “Dur” column in table 430. Weight(“Wt”) is one of many factors used to estimate the duration of a portionduring a presentation. Here, the weight defaults to unity (1), however,it may be adjusted to signal that a portion is of higher (or lower)significance than other portions. A third column relating to customerdata, “CD,” typically contains one or more pointers to customer datastored in the data server 185, e.g., a CRM (customer relationshipmanagement) system. In another embodiment, it may directly containcustomer data. Such information, combined in real time with audiencefeedback, is used to update duration determinations during apresentation. Tables 470 and 480 depict exemplary customer data recordsstored in data server 185 in one embodiment. The first row of tables 470and 480 identify a customer by name, the second row identifies whetheror not the customer is engaged in an active sales matter, e.g., a “hot”prospect, the third row identifies one or more products the customer maypurchase, and the forth row includes customer relationship notes. Othercustomer relationship information may be included in tables 470 and 480in other embodiments.

Another aspect of a successful presentation relates to creating orenhancing sales leads that may arise in relation to the presentation,e.g., as consequence of subject matter relevance to a sales prospect,while presenting to an audience, or during rehearsal. Audience reactionor interaction data, e.g., data relating to audience members such asquestions, comments, “likes” relating to one or more presentationportions, and time spent on one or more presentation portions, arereceived by audience support service 180 and transmitted to metadataservice 490 in accordance with one embodiment. Metadata tables 470 and480 include one or more tags (“@tag”) in one embodiment, foridentifying, e.g., one or more CRM users responsible for sales ormarketing a product. Customer data service 194 automatically correlatesportions of the presentation with data from the customer data resource,e.g., CRM, to determine appropriate tags. Audience reaction data may beparsed for, e.g., product and sales-relevant information and tagged byservice 194. For example, service 194 may determine the subject matterof portion 401 of the presentation includes subject matter relevant tocustomers and sales leads serviced by individuals identified by @tag1and @tag2. It then communicates the tags to metadata service 490, whichinserts them into table 470 at row 4. During a presentation orrehearsal, a presenter may also “tag” a portion's metadata, for example,with @tag3. Presenter support service 178 communicates @tag3 to metadataservice 490, which adds it table 470 at row 4. A date stamp may also beincluded with each tag. Tags are advantageously available to a leadscoring algorithm.

Lead scoring is an algorithm that scores and ranks sales leads accordingto prospects most likely to buy, thereby enabling salespeople toeffectively focus their efforts. Information relating to sales leads,typically stored in a customer data resource, e.g., CRM, are correlatedand weighed to determine lead scores. This information typicallyincludes company size, market size, potential spend amounts, dates ofcontact with sales prospects, other time-relevant events, and behavioralaspects, e.g., whether a sales prospect has responded to on-linesurveys, and so forth. Tags, by virtue of their close association torelevant subject matter included in multimedia presentations, may serveas a powerful input to a lead scoring algorithm.

Present and historical metadata, included in data structure 400,including information pertaining to attendees registered for aparticular presentation to be given, are provided as inputs via metadataservice 490 to the lead scoring algorithm. For example, metadata 490parses portions 401 and 402 of FIG. 4 and transmits parsed data to thelead scoring algorithm, which ranks the portions based relevance oftheir respective content, e.g., as indicated by the parsed data, to theaudience, e.g., as indicated by customer resource data, includingsubject matter interest, likely spend, region, date and time of mostrecent contact. The lead scoring algorithm returns its scores tometadata service 490, which inserts them respectively in the fifth rowof tables 470 and 480. Thus, in preparing a multimedia presentation, alead score is used to rank a portion, e.g., a slide, to determine aduration for each portion of the overall presentation. In anotherembodiment, the method just described is applied in real-time asattendees come and go, and lead scores are communicated to metadataservice 490 by audience support service 180, to dynamically adjust, ortune, the duration of each presentation portion. Document managementservice 175 communicates the lead score for each portion to presentersupport service 178 for use by the presenter, and to automated moderatorservice 183.

In another aspect, a trailer, also referred to as a preview, is amultimedia presentation that provides a summary or introduction, e.g.,highlights, of a pre-existing multimedia presentation, therebyintroducing and enhancing its appeal to a prospective audience, andserving to, e.g., generate interest in an upcoming event such as aconference. One or more trailers relating to a pre-existing multimediapresentation, each tailored to one or more prospective audience members,are automatically created in accordance with one embodiment, therebyadvantageously enabling precise targeting on a large scale. In oneembodiment, the tailoring is performed in relation to customer resourcedata. As customer resource data change over time, e.g., CRM data areupdated as a sales cycle progresses, the one or more trailers, whetherinitially created automatically or manually, are automatically updatedin accordance with another embodiment, thereby further enhancingtargeting.

In one embodiment, metadata service 490 includes an automated trailercreation service. Metadata service 490 receives a request from documentmanagement service 175 to create a first trailer in accordance with oneembodiment. The request identifies a first pre-existing multimediapresentation, e.g., corresponding to portions 401-410 depicted in FIG.4, and may include optional selection criteria, for example, a slidecount, and a region, e.g., a location corresponding to an upcoming eventor conference. A second, and optionally additional pre-existingmultimedia presentations, are specified in another embodiment. Metadataservice 490 reads metadata table 415 corresponding to the firstmultimedia presentation and at row 5, references a pointer to trailerspec table 417. Illustratively and without limitation, trailer spectable 417 specifies a maximum number of slides to include in the firsttrailer (“Slide count”), and a region corresponding to a locale in whichan upcoming event is to take place. More or fewer specifications, e.g.,“Other,” may be included as desired in trailer spec table 417 within thescope of the invention. Metadata service 490 parses portions of thefirst pre-existing multimedia presentation, e.g., as depicted in FIG. 4,and together with criteria specified in table 417, transmits one or morerequests to customer data service 194 to make one or more queries tocustomer and other data resources, e.g., CRM, SalesIQ, Campaigns, andContacts. Metadata 490 receives results of the one or more queries fromcustomer data service 194, which include contact information forpotential attendees cross-referenced to subject matter pertaining to thefirst pre-existing multimedia presentation. For a first contact,metadata service 490 next ranks the relevance of subject matter of eachslide from the first pre-existing multimedia presentation, and creates afirst trailer including relevant subject matter, up to the slide countspecified in table 417, enters a title for the first trailer in row 1,column 1 of table 419, and enters first contact information in row 1,column 2. The process repeats for each contact until a trailer has beencreated for each contact. Notably, one or more contacts may be selectedto receive the same trailer in accordance with one embodiment, andmultiple contacts are entered as a contact list in column 2corresponding to the trailer. Each trailer is transmitted to itsassociated contact(s) via email, e.g., including a URL to the trailer, adirect push to an audience support interface, e.g., via audience supportservice 180, or via, e.g., a mobile application. Audience supportservice 180 receives feedback from audience members, e.g., comments and“likes” via e.g., the mobile application, and transmits the feedback topresenter support service 178 for presentation on a wireless handheldpresenter device, e.g., device 150.

In another embodiment, a portion duration is determined for each portionof a trailer as described above with respect to a multimediapresentation. A presenter, e.g., presenter 155, may desire to manuallyspecify portions for manually creating a trailer from a multimediapresentation, e.g., as depicted in FIG. 4, to run, e.g., in a loopimmediately before a live presentation. In that embodiment, Metadataservice 490 receives a list of slides from presenter interface 178,enters them in row 4 of table 415, and selects slides from themultimedia presentation to create a second trailer. As in the case of anautomatically created trailer, metadata service 490 parses themulti-media presentation to determine a portion duration for eachportion of the trailer, advantageously timing portions, e.g., longerdurations for subject matter of greater relevance to an audience.

FIG. 5 is a flowchart 500 depicting a method for estimating a durationof a portion of a multimedia presentation, and a multimedia presentationduration, in accordance with one embodiment. In step 505, the methodretrieves historical data corresponding to a portion of thepresentation, e.g., duration (“Dur”), weight (“Wt”), and customer data(“CD”) from tables 440 and 450 depicted in FIG. 4. The method nextdetermines in step 510 whether the data just retrieved includes orrefers to, e.g., by pointer or link, historical customer data. If so,the method branches to step 515 and retrieves the historical customerdata. For example, if the method identifies that the “CD” columncorresponding to row 10 of table 440 includes pointer “B” to table 480,it retrieves historical customer data from table 480, which in oneembodiment, is located in data server 185, e.g., storage 195. In step520, the method retrieves customer data corresponding to audiencemembers. In one embodiment, described above with reference to FIGS. 1-3,audience identities have been retrieved from wireless handheld audiencedevices, e.g., 110, 120, 130 and are available to the method. Next, themethod, in step 525, determines a duration for the current portion by,e.g., combining durations, weights, and customer data (historical andcurrent), and storing the resultant duration in table 420. In step 530,the method advances to the next portion and determines at step 535whether the last portion has been reached. If not, the method repeatsthe previous steps. If so, the method combines individual portiondurations to determine a multimedia presentation duration, and stores itin table 420. The method finishes at step 595.

In one embodiment, the method operates continuously. For example, as apresentation (rehearsal or to an audience) progresses, the methoddetermines a presentation duration corresponding to a current andremaining portions to be presented. The duration is scaled, e.g.,ratably, based on a ratio of an actual time remaining for a presentationas a whole, e.g., 30 minutes (it is now 2:30 P.M. and the presentationmust end by 3:00 P.M.), to the sum of durations for the current andremaining portions. For example, if the presentation must end in 30minutes, the estimated duration for the current portion is 5 minutes,and the sum of durations of the current and remaining portions is 35minutes, then the method scales the current portion to 5×30/35=4.3minutes, and presents this figure to the presenter. The method in turncomputes a new estimate for the portion as it is being presented. Inanother embodiment, the method operates (“triggers”) in response to achange in customer data, e.g., from a third party data service, e.g.,outsourced CRM, and in a further embodiment, receives the changed dataitself, e.g., via a webhook, wherein the webhook provides updated orchanged data upon the occurrence of any updated or changed data.

FIG. 6 is a flowchart 600 depicting a method for automating feedbackmoderation to a presenter of a multimedia presentation in accordancewith one embodiment. During a multimedia presentation, it isadvantageous for the presenter to automatically receive appropriatelyprioritized feedback from audience members. In one embodiment,prioritization, including blocking feedback, is based on the feedback,historical customer data stored in a customer relationship (“CRM”)system, e.g., data server 185, and historical data relating to thepresentation itself, e.g., as depicted in FIG. 4. In step 605, themethod receives feedback corresponding to an audience member via anetwork from a handheld wireless audience device, e.g., devices 110,120, and 130, identifies the audience member corresponding to thewireless handheld audience device in step 610, and in step 615,retrieves customer data corresponding to the audience member via thenetwork. In another embodiment, the method receives feedbackcorresponding to an audience member, e.g., member 115, to a remoteserver (e.g., presentation server 165 and data server 185 depicted inFIG. 1 in one embodiment), from a wireless handheld audience device,e.g., device 110. In a next step, the method identifies the audiencemember corresponding to the wireless handheld device as described abovewith respect to, e.g., FIGS. 1-3, and retrieves from, e.g., data server185, data corresponding to the audience member. In another embodiment,historical data relating to a portion of a presentation may include dataretrieved via the data structure 400 depicted in FIG. 4. The method, atstep 620, associates and cross-correlates the customer feedback with theretrieved data to provide an automated moderator result. In oneembodiment, the associating and correlating feedback includes filteringand prioritizing based on various criteria. In one embodiment, thecriteria include customer data corresponding to one or more audiencemembers, and may be defined, and selected, by the presenter ormoderator. Based on the associating and cross-correlating, the methoddetermines at step 625 whether to display the feedback to the presenter.If so, the method at step 630 sends the feedback to the presenter viathe network. The process finishes at step 695. In one embodiment, themethod operates continuously.

FIG. 7A depicts multi-layered slides 701-710, also referred to asmultidimensional slides, relating to a multimedia presentation inaccordance with one embodiment. A multimedia presentation contains oneor more portions including audio, video, and slides. In one embodiment,a presentation includes slides, e.g., Zoho Presentation, MicrosoftPowerPoint, one slide per portion. In another embodiment, a portion maycontain a group of one or more slides. In one embodiment, the one ormore slides may be related or associated. A relation or association ofone slide to another may be referred to as a layer, or a dimension. Agroup is useful to, e.g., provide the presenter with “detailed” and“succinct” versions of a slide. In one embodiment, slide 701 includes“succinct” slide 701 a (bar chart quantifying “subscriptions”), and“detailed” slide 701 b for the presenter's eyes only, e.g., displayingonly on wireless handheld presenter devices 150, or 160, which includesthe information of slide 701 a along with the presenter's notes, e.g.,“speak slowly and clearly.” In another embodiment, all slides in a groupare intended for an audience. For example, slide 710 depicts a group ofslides 710 a-c, each reciting the same phrase in three languages:English, Italian, and French. Presentation service 178 automaticallyselects one of slides 710 a-c based on a prior setting (stored, e.g., indata structure 400, or responsive in real-time to customer data receivedfrom customer data service 194 corresponding to attendees, e.g.,audience composition by country, indicative of language and culturaltastes), thus relieving the presenter of real-time selection whilecommunicating the presentation to the audience. In another embodiment,presenter support service 178 receives real-time audio of thepresentation, e.g., via microphone in wireless handheld presenter device150, performs language recognition and identifies that, e.g., French isbeing spoken, and selects French slide 710 c. In one embodiment,presentation service 178 prompts the presenter to select a slide from agroup during a presentation. In another embodiment, presentation service178 identifies “for presenter's eyes only” slides, designated, e.g., indata structure 400, and presents them only to the presenter and not tothe audience. In yet another embodiment, presentation service 178receives voice input via, e.g., a microphone in wireless handheldpresenter device 150, performs voice recognition and determines aphrase, e.g., a keyword or command. In response to the phrase, service178 selects a resource, e.g., a slide, audio or video segment, andtransmits the resource or a preview of it to the screen of device 150.Presenter 155 may then review the transmission from service 178 anddetermine whether to present it to the audience. Metadata, e.g., timeand date stamps, and location-related information, are stored in adimension in accordance with one embodiment.

In another embodiment, dimensions provide variations of the presentationrelating to a presentation environment. For example, slide (dimension)701 c, depicted in FIG. 7A, is a high contrast version of slide(dimension) 701 a, suitable for presentation in a brightly litenvironment. Similarly, a small-format slide (dimension) may be providedfor wireless handheld mobile devices, e.g., devices 110, 120, 130, 140,150, and 160, and display device 162. Different aspect ratios,resolutions, color schemes, color saturation, brightness, contrast andgamma variations, and font types including anti-aliasing fontvariations, are also provided for various environments and devices. Asexplained above, audience support service 180 is location-aware,detecting whether a wireless handheld audience device is, e.g., in anarea in which a multimedia presentation is taking place. Service 180 maytherefore communicate with one or more sensors in one or more wirelesshandheld audience devices in the area of the presentation, e.g., room101, perform a global or localized lighting analysis based on dataobtained from the one or more sensors, determine lighting conditions,and report that information to document management service 175. Documentservice 175 communicates with sensors in one or more devices, e.g., awired or wireless device, in accordance with another embodiment. Service175 in turn selects one or more dimensions, appropriately formatted forthe environment and the devices, and delivers the one or more dimensionsrespectively to the devices, e.g., display device 162, and via audiencesupport service 180, to relevant wireless handheld audience devices,e.g., those within room 101.

In another embodiment, a dimension serves as a repository forannotations to the multimedia presentation, such as those described withrespect to FIG. 8 below. For example, presenter service 178 includesannotation commands in the presenter interface, and a first annotationis made to the multimedia presentation with wireless handheld presenterdevice 150. Presenter service 178 receives the annotation from device150. Document management service 175 receives the first annotation frompresenter service 178, and stores and associates it in a first dimensionof the multimedia presentation. One or more multidimensional slidetemplates are created and maintained by document management service 175in one embodiment. A template may specify, e.g., formatting andattributes such as language, font size, color scheme on adimension-by-dimension basis, thereby aiding in the creation of newmultimedia presentations.

A program source, including video, audio, one or more document pages,and a multimedia presentation including one or more dimensions, isannotated with one or more annotation sources in any combination, inaccordance with one embodiment. Like a program source, an annotationsource may be any arbitrary source, including video, audio, documentpages, and portions of other multimedia presentations. Annotations areassociated with a multimedia presentation in a variety of ways. In oneembodiment, the annotations are stored directly in a multimediapresentation dimension along with parameters for applying theannotations to the multimedia presentation. In another aspect, amultimedia dimension stores parameters for applying the annotations tothe multimedia presentation, and stores references to the annotationsrather than storing the annotations themselves. In that case, theannotations are stored outside the presentation, e.g., as computer diskfiles or in “cloud” storage. In yet another aspect, e.g., annotationtable 724 depicted in FIG. 7B, a multimedia dimension stores one or morereferences to data tables that in turn refer to annotation sources. Thedimension also includes parameters and specifications for applying theannotations to the multimedia presentation. Document management service175 manages the annotations and tables on behalf of a presenter andmoderator in cooperation with presenter support service 178, and onbehalf of an audience member in cooperation with audience supportservice 180. A presenter, moderator, and with appropriate permissionsenforced by audience support service 180, an audience member, mayindividually store and annotate a multimedia presentation, and create aplatform-independent movie based on the annotated multimediapresentation. A link to the presentation movie is made available forfurther editing and sharing.

Exemplary apparatuses including repositories for annotations andassociations between annotations and multimedia presentations, andmethods for annotating multimedia presentations, are depicted in FIGS.7A-7C. Any multimedia presentation may be annotated and stored by apresenter (155), a moderator (145), or an audience member (115, 125,135), supported by document service 175, automated moderator service183, presenter service 178, and audience service 180. A multimediapresentation may be annotated with any number of sources, includingaudio, video, audio and video, animations, various document typesincluding, e.g., presentation slides and document pages, and annotationssuch as those described with respect to FIG. 8. Because a multimediapresentation may itself comprise one or more of the foregoing types, anannotated multimedia presentation may comprise, e.g., slides and videoannotated by video, video annotated by slides, slides annotated byvideo, audio, and slides, slides annotated by slides, video annotated byvideo, and so forth.

Portions of a multimedia presentation depicted as slide group 701annotated by two videos and a slide, and slide group 710 annotated byaudio and a document, are shown in FIG. 7A. Slide group 701 depicts agroup of slides 701 a-c for presentation to various audiences. Anadditional slide 701 d serves as a repository for annotations that maybe applied to group 701, including annotations for any of slides 701a-c. Annotation elements 721 (video), 722 (video), and 723 (slide) arearranged on slide 701 d in locations relative to where each willactually appear on an annotated slide. Presenter support service 178,and audience support service 180, respectively enable a presenter ormoderator, and an audience member, to conveniently arrange annotationssuch as elements 721, 722, and 723 on a dimension, e.g., slide 701 d.Annotation data, parameters, and specifications, including a programsource (dimension to be annotated), annotation overlay locations,scaling, annotation source references, and annotation time sequencing,are stored in annotation table 724. Although table 724 is invisible to auser viewing a dimension, e.g., slide 701 d, it is depicted for clarityof description as a visible element on slide 701 d in FIG. 7A toillustrate that it, or a reference to it, is stored in relation toannotation slide 701 d. Dimension (slide) 710 d similarly depictsannotation elements 741 (audio), 742 (slide), and annotation table 743.

FIG. 7B depicts dimension and annotation tables, and exemplary portionsof annotated multimedia presentations, in accordance with oneembodiment. A dimension table identifies portions of a multimediapresentation, identifies dimensions in each portion, and associates oneor more annotations with a dimension. Dimension table 740 referencesportions 701-703 and 710 of the multimedia presentation depicted in FIG.7A. Each dimension referenced in table 740 is identified in “Dimensions”column 2, and annotations are identified in “Annotations” column 3. Inthis example, annotations are associated with a dimension by virtue of areference in “Annotations” column 3. For example, to associate portion(slides) 701 to the annotations identified in annotation table 724,“d,724” is inserted in Annotations column 3 of row 1. Additionalannotations, e.g., “e,791,” are specified in Annotations column 3 inaccordance with another embodiment. In dimension table 740, row 1 column1 (“Portion”) identifies multimedia presentation portion 701, row 1column 2 (“Dimensions”) identifies multiple dimensions comprised ofdimensions a, b, c, and d (slides 701 a-d), and row 1, column 3(“Annotations”) identifies dimension (layer) d (slide 701 d) as a slidecontaining annotations. Portion 702 has only a single dimension (itself)and no annotation, denoted by “-” (null) in the Dimensions andAnnotations columns. Portion 703 includes dimension 703 a, and anannotation dimension, identified in the Annotations column as dimension“b.” Annotation specifications corresponding to portion 703 are storedin row 1 of table 732. Row 4 similarly describes portion 710 andannotation elements 741 and 742 (rows 1 and 2 of table 743).

Annotation table 724 depicted in FIG. 7B includes columns “Pgm Src,”“InsPt,” “Overlay Loc,” “Scale,” “Annotation Source,” “Start,” “Dur,”“XF,” and “F/B,” serving to identify portions of the multimediapresentation to be annotated, the annotation source, and data,parameters, and specifications for applying the annotation source to themultimedia presentation. Row 1 of table 724 corresponds to portion 701of the multimedia presentation depicted in FIG. 7A. The “Pgm Src” columnidentifies dimension 701 a (the top slide in FIG. 7A) as the programsource, i.e., the item to be annotated. The “Annotation Source” columnreferences the source that will annotate the program source. In thisinstance, document service 175 will retrieve cloud-based movie file(http://zoho.local/annot1.mov) and use it to annotate dimension 701 a.The annotation will overlay dimension 701 a at its location (100, 100),specified in the “Overlay Loc” column of dimension 701 a. The locationmay be made with reference to any reference point on dimension 701 a aswill be appreciated by one of skill in the art. Here, (100, 100) locatesthe upper left hand corner of “annot1.mov” 100 units to the right anddown, relative to the upper left corner of dimension 701 a. Theannotation will be scaled to 25% (0.25) of its original size asspecified in the “Scale” column. The “F/B” column specifies whether theannotation appears as foreground, background, or transparent elements.Foreground and background annotations will respectively appear “in frontof” and “behind” program source features. Transparent annotations (notshown), indicated by the letter “T” in the “F/B” column, allowunderlying features to be visible through the annotation. The letter “F”in the “F/B” column of table 724 row 1 indicates “annot1.mov” willappear in front of dimension 701 a features. An exemplary end result of“annot1.mov” annotating dimension 701 a is depicted in the first slide701 a in sequence 760. Note the annotation (721) overlays and partiallycovers bar chart 762.

In some multimedia presentations, dimensions may include discreteelements, and there may be more than one annotation. The system andmethods described herein provide a way to time and sequence multipleannotations appearing on a portion of a multimedia presentation. Timingand sequencing of annotations relative to presentation elements areprovided in accordance with one embodiment. The “InsPt” column providesa way to trigger an annotation on the appearance of an element in apresentation. This advantageously provides granularity within apresentation. For example, a presenter may wish to display a firstelement (bar chart), cause that element to trigger a first annotation (abrief video clip), and then upon displaying a second element (a labelcorresponding to the bar chart), trigger a second annotation video. Toillustrate, sequence 760 in FIG. 7B depicts a time sequence of threephases of multimedia presentation dimension 701 a. In the first phase,the first element, a bar chart 761, is displayed and has triggered afirst animation 721, which overlays the bar chart. The second element,label 762 (“Subscriptions”), is not yet displayed as indicated by thedashed rectangle in the slide. In the second phase, label 762 appears,triggering a second animation 722, which partially overlays label 762 atlocation (400, 100), and at 25% of native scale as specified in the“Overlay Loc” and “Scale” columns of table 724 row 2. To triggeranimations 721 and 722, the “InsPt” column of table 724 at row 1 isloaded with the number “1” (corresponding to element 1 of dimension 701a), and row 2 is loaded the number “2” (corresponding to element 2 ofdimension 701 a).

Additional timing granularity in the triggering and scheduling ofannotations is provided by defining “Start,” “Duration,” and “XF”(crossfade) times for each annotation, as shown in table 724. The“Start” value defines a time interval between a trigger and the start ofan annotation play. In the example of table 724, annotation “annot1.mov”is triggered when the first element of dimension 701 a (bar chart 761)appears, however, the “Start” value of 3 delays the onset of“annot1.mov” until three (3) seconds after bar chart 761 appears.Similarly, “annot2.mov” is triggered when the second element ofdimension 701 a (label 762) appears. Because the “Start” value in row 2is 0, however, “annot2.mov” fires immediately upon the appearance of thesecond element. A third annotation, http://zoho.local/annot3.pdf:2, isspecified in table 724 row 3, referencing the second page of a pdf file(“:2” indicating the second page). The number “−1” in the “InsPt” columnindicates the third annotation triggers at the end of the secondannotation. In this manner, annotations may be chained together. The“XF” column in row 3 is loaded with “−0.5,” thereby causing the thirdannotation to fire one-half second before the end of the secondannotation. An appropriate cross-fade algorithm is applied to fade outthe second annotation as the third annotation begins to effectuate asmooth transition. Loading “XF” with a positive (rather than a negative)number introduces a delay (rather than a cross-fade) betweenannotations. In this example, loading XF with “0.5” introduces aone-half second delay between the second and third annotations.

Setting “InsPt” to “-” (dash or null), signals an annotation willtrigger upon the appearance of a program source (in the present example,a dimension or slide of a multimedia presentation). In this instance,the “Start” value determines a time interval between the appearance ofthe dimension and the start of the annotation. Multiple annotations maybe triggered on the appearance of a program source (here, a dimension),with actual start times determined by the “Start” value specified foreach. In this example, the dimension is a slide, 703 a. “InsPt” in table732 is null (“-”), “Start” is loaded with the number “1,” with aduration (“Dur”) of 7 seconds. The annotation, “annot4.mov,” thereforestarts 1 second after the appearance of slide 703 a and runs for seven(7) seconds. A second annotation (not depicted), for example a documentpage, is similarly specified in table 732 but with a “Start” value of 4.(The second animation may also be positioned at a different overlaylocation on slide 703 a than the first animation.) The second annotationtherefore starts four (4) seconds after the appearance of slide 703 a,which is also three (3) seconds (4−1) after the start of, and during thefirst annotation. A presenter, moderator, or audience member istherefore afforded great flexibility in determining the timing andsequencing of annotations to multimedia presentations. As demonstratedabove, the “Dur” value specifies the duration of an animation display.In the case of video or audio having a duration exceeding the “Dur”value, document service 175 fades the video or audio annotation uponreaching the specified duration (“Dur”).

To recap, a presenter or moderator, or an audience member (supportedrespectively by presenter and audience support services 178 and 180),and automated moderator service 183, annotates a multimedia presentationby arranging annotations visually on a multimedia presentationdimension, e.g., slides 701 d and 710 d. Annotations may be createdduring live presentations, and at other times. For example, an audiencemember may record a “Q&A” discussion relating to an element of a slideduring a live presentation. The annotated slide including the “Q&A”discussion is stored as a dimension of the multimedia presentationportion corresponding to the slide, in an account corresponding to theaudience member. A presenter or moderator may similarly create and storeannotations to multimedia presentations, during a presentation and atother times. Annotations are triggered upon the appearance of a programsource which can be, e.g., audio, video, a dimension of a multimediapresentation including a slide, or upon the appearance of elementswithin a program source such as one or more bookmarks, or one or moreelements within a slide, e.g., a graph or label text. When annotationparameters are not specified, default parameters are applied, e.g.,multiple annotations relating to one portion are applied inleft-to-right, top-to-bottom order with default scaling of 25% and five(5) second durations. Document support service 175, in cooperation withservices 178, 180, and 183, manages program sources includingdimensions, stores the annotations and related parameters (or referencesto them) in the dimensions, and manages related dimension and annotationtables. Annotations are stored within or external to the dimensions,e.g., in computer or “cloud” storage.

Sequence 760 in FIG. 7B depicts a seven (7) phase sequence for thedisplay of slide dimensions 701 d, 702, 703 b, and 710 d, making use offour (4) program sources, here, dimensions (slides) 701 a, 702, 703 a,and 710 a, demonstrating the end result of applying annotations 721-723,731, and 741-742 (depicted in dimensions 701 d and 710 d and specifiedin tables 724, 732, and 743), to the multimedia presentation depicted inFIG. 7A.

Phases 1-3 correspond to slide dimension 701 d making use of slide 701 aas the program source. Dimension table 740 references dimension 701 dand annotation table 724 for annotations. The program source (“Pgm Src”)to be annotated in phases 1-3 is dimension (slide) 701 a, identified incolumn 1, rows 1-3 of table 724. In phase 1, the annotation is definedin row 1 of table 724. Annotation 721 (“annot1.mov”) appears three (3)seconds (“Start”=3) after the first element, a bar graph (761), on slide701 a (“InsPt”=1) appears. The bar graph remains for 17 seconds(“Dur”=17). The second element of slide 701 a, a label 762 indicated bya dashed rectangle, is not yet visible. Annotation 721 is in theforeground (“F/B”=F), sitting atop and partially covering bar graph 761at overlay location (100, 100) (“Overlay Loc”=100,100), and scaled to25% (“Scale”=0.25) of its native size.

In Phase 2, the annotation is defined in row 2 of annotation table 724.Annotation 722 (“annot2.mov”) appears immediately (“Start”=0) upon theappearance of the second slide element, “Subscriptions” label 762,(“InsPt”=2) of slide 701 a, and remains for five (5) seconds (“Dur”=5).Note that first annotation 721 is defined to have a 17 second duration.A presenter, moderator, or audience member, may override this durationsimply by advancing to the second slide element, here, “Subscriptions”label 722. If the presentation is running in auto-play mode, however,the full 17 second duration corresponding to annotation 721 elapsesbefore document support service 175 advances to the second element,which triggers second annotation 722. Annotation 722 is in theforeground (“F/B”=F), sitting atop and partially covering label 762(“Subscriptions”) at “Overlay Loc” (100, 400), and scaled to 25%(“Scale”=0.25) of its native size.

In Phase 3, the annotation is defined in row 3 of annotation table 724.Annotation 723 (“annot3.pdf:2”) is page 2 (“:2”) of a pdf document. Itstrigger point is set to occur after annotation 722 concludes(“InsPt”=−1), however because the cross-fade parameter (“XF”=−0.5)defines a one-half (0.5) second overlap, annotation 723 fires one-halfsecond before the conclusion of annotation 722. It remains active forfour (4) seconds (“Dur”=4) at “Overlay Loc” (600, 400), and is scaled to20% (“Scale”=0.20) of its native size.

Phase 4 corresponds to slide 702. Dimension table 740 references nomultimedia presentation dimension or annotation table, therefore slide702, depicting a pie chart, simply displays sans annotation.

Phase 5 corresponds to slide dimension 703 b making use of slide 703 aas the program source. Dimension table 740 references dimension 703 band annotation table 732 for annotations. The program source (“Pgm Src”)to be annotated is dimension (slide) 703 a. A single annotation 731(“annot4.mov”) is defined in row 1 of table 732. This annotation istriggered by the slide itself (“InsPt”=“-”, or null) rather than by anelement within a slide. It appears in the lower right corner of slide703 a (“Overlay Loc” (600, 600)), one (1) second (“Start”=1) after slide703 a appears, remains for seven seconds (“Dur”=7), and is scaled to 30%(“Scale”=0.30) of its native size.

The final two phases, 6-7, correspond to slide 710 d making use of slide710 a as the program source. Dimension table 740 references dimension710 d and annotation table 743 for annotations. The program source (“PgmSrc”) to be annotated in phases 6-7 is dimension (slide) 710 a,identified in column 1, rows 1-2 of table 743. In phase 6, theannotation is defined in row 1 of table 743. Annotation 741(“annot6.mp3”) is an audio file, and therefore invisible. It starts toplay three (3) seconds (“Start”=3) after the first element on slide 710a, the text “Mastery comes from being one with your work . . . ”appears, and plays for five (5) seconds (“Dur”=5). A second annotation742 (“annot7.pdf:5”), page 5 (“:5”) of a pdf document, is defined in row2 of table 743. The second annotation also triggers with reference tothe first element (“InsPt”=1) of slide 710 a. It appears ten (10)seconds after the first element on slide 710 a appears, for a durationof ten (10) seconds (“Dur”=10) in the lower right corner (“Overlay Loc”600, 700) of slide 710 a. It is scaled to 20% (“Scale”=0.20) of itsnative size, and appears in the foreground (“F/B”=F), partially coveringthe slide text.

Annotating a multimedia presentation uses audio or video as a programsource in accordance with another embodiment. In the example thatfollows, an audience member, e.g., member 115, focused handheld audiencedevice 110 on herself and narrated annotations for the first two slidesof the multimedia presentation depicted in FIG. 7A. This could haveoccurred during a live presentation of the multimedia presentation, orwhile playing a stored version of the multimedia presentation. Audiencesupport service 180 enables audience member 115 to access the multimediapresentation, and in cooperation with document service 175, arranges forseparate storage for the audience member, here member 115, under her ownaccount. Notably, many audience members (and moderators and presenters),may simultaneously annotate multimedia presentations, limited only bysystem and storage capacity of their respective accounts. Documentservice 175, in cooperation with audience support service 180, may limitthe number of annotations or storage allotments for users, includingaudience members, as desired, e.g., to conserve system resources asdetermined by a system administrator. This “narrative” type ofannotation typically auto-plays in a sequence defined by an annotationtable, with audio or video, e.g., relating to an audience member'snarration, serving as the program source.

Sequence 765 in FIG. 7B depicts a two (2) phase sequence in which amovie created by an audience member, e.g., 115,(“http://zoho.local/audience_created.mov”), serves as the programsource, annotated by dimensions from a multimedia presentation, here,slides 701 a and 702 of the multimedia presentation shown in FIG. 7A.Phase 1 is defined in row 1 of annotation table 750. The program sourceto be annotated (“Pgm Src”) is a movie clip, “audience_created.mov:00.”The movie (clip 771 showing audience member 115) begins at zero seconds(“:00”), and is annotated by “Annotation Source” dimension (slide) 701a. Slide 701 a starts at the beginning (“Start”=0) of the movie, andremains for ten (10) seconds (“Dur”=10). Movie 771 and annotation(dimension) 701 a appear side-by-side, with slide 701 a positioned onthe left of movie 771 (“Overlay Loc” set to −1), and is scaled to 120%(“Scale”=1.20) of its native size. Setting the table entry for “OverlayLoc” to “−2” (not shown) causes the annotation (dimension 701 a) toappear to the right of movie 771 in accordance with another embodiment.

Phase 2 is defined in row 2 of annotation table 750. The program sourceto be annotated (“Pgm Src”) is a second movie clip,“audience_created.mov:27.” The second movie (clip 772 showing audiencemember 115) begins at 27 seconds relative to its beginning (“:27”), andis annotated by “Annotation Source” dimension (slide) 702. Audiencesupport service 175 automatically stamps the program source time (“:27”)when, during a presentation, the next portion, here slide 702, appears.Thus, while traversing the annotation table during auto-play, documentservice 175 launches the second movie clip at the appropriate time (:27)and the annotation sequence plays. In another embodiment, a differentclip, e.g., “audience_created2.mov,” may instead serve as a programsource in row 2 of table 750. This allows a presenter, moderator, oraudience member to advantageously edit an annotation at any time. Thesystem seamlessly transitions by blending or cross-fading between movieclips as it traverses the annotation table during playback. Returning tothe instant annotation example, annotation (dimension) 702 starts 12seconds (“Start”=12) after movie clip 772 begins, and remains for ten(10) seconds (“Dur”=10). Scaling and location for this annotation (120%,annotation side-by-side to the left) are the same as for the firstannotation.

Sequence 770 in FIG. 7B also depicts a two (2) phase sequence in which amovie created by an audience member, e.g., 115,(“http://zoho.local/audience_created.mov”), serves as the programsource, annotated by dimensions from multimedia presentation slides 701a and 702 of the multimedia presentation shown in FIG. 7A. In thisembodiment, however, annotations appear within, rather than alongside,the program source. For simplicity, only annotation parameters differingfrom those described in the “alongside” example above are described.Phase 1 is defined in row 1 of annotation table 755. Annotation source(dimension) 701 a is scaled to 55% (“Scale”=0.55) of its native size,and is located at “Overlay Loc” (200, 300) of movie clip 771. Because“F/B” is set to “F,” slide 701 a is in the foreground of movie 771,partially covering the image of presenter 115. Phase 2 is defined in row2 of annotation table 755, and specifies dimension 702 as the annotationsource. Slide (dimension) 702 is scaled and positioned in the samelocations as slide 701 a, however, “F/B” is set to “B,” indicating slide702 is in the background. Accordingly, the image of presenter 115depicted in movie 772 appears in front of and partially covers slide702.

In another aspect, a movie clip includes one or more bookmarks, e.g.,first, second, and third bookmarks at 15, 27, and 33 seconds into theclip. Specifying “InsPt” corresponding to the first bookmark, e.g., “1”corresponding to the bookmark at 15 seconds, provides for triggering anannotation source upon reaching the first bookmark at :15 in accordancewith one embodiment. An absolute time, e.g., “27” is specified as an“InsPt” in accordance with another embodiment, providing for triggeringan annotation source when the movie playback reaches 27 seconds.

FIG. 7C sets forth flowchart 780 depicting a method for annotating amultimedia presentation in accordance with one embodiment. In step 782,an interface for a multimedia presentation is provided, e.g., viaaudience support service 180 or presenter support service 178, to ahandheld wireless device, e.g., audience devices 115, 125, and 135,moderator device 140, and presenter device 150, via a network. Amultimedia presentation, e.g., as depicted in FIG. 7A, includes aplurality of elements. For example, the presentation depicted in FIG. 7Aincludes portion 701 having dimensions a-d, dimension 701 a including afirst element (bar graph) and a second element (“Subscriptions”) label.A portion of the multimedia presentation, e.g., portion 701 a, is sentto the wireless handheld device via the network in step 784. Commandsare received in step 786, e.g., by audience support service 180 orpresenter support service 178, corresponding to selecting the firstelement, and identifying an annotation source, e.g., a narrative moviemade by an audience member, presenter, or moderator. Responsive to thecommands, e.g., by document service 175, the first element is associatedwith the annotation source, and the multimedia presentation is updatedto include the associated annotation in step 788. The update to themultimedia presentation may include storing annotation information in adimension, e.g., 701 d, of the multimedia presentation. Annotationinformation may include annotation sources, e.g., “.mov” files,references to annotation sources stored elsewhere, e.g., in “cloud”storage, and annotation specifications or references to externallystored annotation specifications, e.g., in a database table or in“cloud” storage. At step 789, the method ends.

FIG. 7C also sets forth flowchart 790 depicting a method for playing anannotated multimedia presentation in accordance with another embodiment.In step 792, an interface for a multimedia presentation is provided,e.g., via audience support service 180 and presenter support service178, to a handheld wireless device, e.g., audience devices 115, 125, and135, moderator device 140, and presenter device 150, via a network. Amultimedia presentation, e.g., as depicted in FIG. 7A, includes aplurality of elements. For example, the presentation depicted in FIG. 7Aincludes portion 701 having dimensions a-d, dimension 701 a including afirst element (bar graph) and a second element (“Subscriptions”) label.A portion of the multimedia presentation, e.g., portion 701 a, is sentto the wireless handheld device via the network in step 794. Commandsare received in step 796, e.g., by audience support service 180 orpresenter support service 178, corresponding to selecting the firstelement, e.g., by an audience member, presenter, or moderator. In step798, responsive to the commands, a first annotation associated with thefirst element is selected, e.g., by document service 175, and sent tothe wireless handheld device. At step 799, the method ends.

FIG. 8 depicts presentation tools 800 in accordance with one embodiment.Presentation tools enable presenter 155 to update a multimediapresentation, including a portion of a multimedia presentation, inresponse to commands by, e.g., adding and removing features, annotating,drawing, sketching, writing, adding text, highlighting, and erasing.Updates made to a multimedia presentation are discarded by documentmanagement service 175 when viewing is complete, e.g., upon viewing adifferent portion, in accordance with one embodiment. Updates may besaved by document management service 175 upon or after concluding apresentation, in accordance with another embodiment. Updates are savedas one or more dimensions of a multimedia presentation in accordancewith another embodiment, e.g., as described with respect to FIG. 7A.Saving updates advantageously enables re-use in future presentations.Presentation tools 800 may be used on a conventional computer, e.g., adesktop or laptop computer having any combination of, e.g., keyboard,mouse, touchscreen, and stylus. In another aspect, presentation toolsmay be used on any handheld wireless device, e.g., wireless handheldmoderator device 140, wireless handheld presenter devices 150 and 160,or the presenter devices 810 and 860 depicted in FIG. 8, e.g.,respectively an iPad and iPhone available from Apple, Inc., ofCupertino, California. Presenter device 810 includes screen 855,depicting a portion of a presentation, a side menu 820, and a submenu825. Side menu 820 is activated by swiping 815 from the left edge ofscreen 855. In another embodiment, e.g., a laptop or desktop computer, amenu such as side menu 820, is activated via keyboard, e.g., by pressingCtrl+Alt+M, or by activating an icon with, e.g., a mouse click or astylus. Document management service 175 or presenter support service178, in communication with a presenter device, e.g., presenter device810, receives commands transmitted by device 810 and in response,updates one or more portions of the multimedia presentation, anddisplays the updates on one or more devices, e.g., presentation device162, wireless handheld audience devices 110, 120, and 130, moderatordevice 140, and one or more presenter devices, e.g., devices 140, 150,160, 810, and 860. In one embodiment, document management service 175 orpresenter service 178 communicates with audience support service 180 forupdating audience presentation devices, e.g., 110, 120, and 130.

Side menu 820 includes icons 821-824 corresponding to aspects ofpresentation tools. Activating drawing tools icon 821, e.g., by swipe,touch, keyboard, or mouse click, activates submenu 825, which includesannotation and drawing tools. A pencil tool 830 enables presenter 155 towrite and draw on a presentation, e.g., the portion depicted on screen855. A group of patterns and colors available in palette 840 (depictedwithout limitation in FIG. 8 as black and white line patterns inconformance with USPTO drawing standards), may be selected by, e.g.,touch, mouse click, or stylus, and applied to pencil tool 830. One ormore patterns or colors is similarly selected from palette 840 forapplication to highlighter 835. Annotations to a presentation bypresenter 155 may therefore be made to a presentation in any arbitrarynumber and combination of colors and patterns. Presenter 155 may usehighlighter tool 835 to annotate a presentation in an intuitive way.

Any portion of a presentation, including annotations, may be erased byselecting eraser tool 845. As noted above, document management service175, presenter service 178, and audience support service 180,communicate with one another and with display devices to effectuateupdating relevant displays in response to annotations made to thepresentation with presentation tools 800. Selecting laser tool 850activates an electronic pointer, e.g., a pointer formatted as a “laser”beam appearing, e.g., as a high intensity red dot. In anotherembodiment, a pointer is formatted in a different color or patternselected, e.g., from palette 840, and a different shape, e.g., adiamond, arrow, or hand. In another embodiment, palette 840 isscrollable and includes icons defining shapes and animations for, e.g.,a shape of an electronic pointer activated by laser tool 850, penciltool 830, and highlighter tool 835. The electronic pointer is furtherdescribed above with respect to FIG. 1. In another embodiment,presentation tools 800 include animating pencil tool 830, highlightertool 835, and eraser tool 845. Transitions among portions of apresentation, e.g., while scrolling, beginning, and ending apresentation, and e.g., between blanking and un-blanking thepresentation, may be animated by presentation tools 800 in anotherembodiment.

Activating portion select icon 822 enables presenter 155 to convenientlyselect a portion of the presentation. Portion select icon 822 identifiesthe portion currently displaying, here, portion 20, in one embodiment.Activating a blackout icon 823 (depicted as a TV screen with an “X”inside) turns off—blacks out, or “blanks”—the multimedia presentationby, e.g., shutting off display device 162 and, e.g., wireless handheldaudience devices 110, 120, and 130. In one embodiment, blanking isaccomplished via, e.g., a blank screen or a blank portion, e.g., a blankslide. Blackout tool 823 therefore advantageously enables presenter 155to focus audience attention on the presenter, thereby enhancingcommunication with an audience. Activating exit tool 824 closes sidemenu 820 and submenus, e.g., submenu 825.

Wireless handheld presenter device 860 depicts presentation tools 800 inanother embodiment, here, on a screen 875 smaller than the screen 855described above. Side menu 870 is activated by swiping 865 from the leftedge of screen 875. Similar to side menu 820, side menu 870 includesannotation tools 800. Item Drawing Tools 871 activates a drawing toolssubmenu (not depicted but similar in one embodiment to submenu 825).Side menu 870 as depicted enables presenter 155 to select a portion of apresentation. Item 872 indicates that portion 19 of 75 portions withinthe multimedia presentation is currently displaying. Portion 19 is alsoindicated by a check mark in a portion selection submenu 880. In oneembodiment, portion selection submenu 880 scrolls, e.g., by swiping,allowing any portion, e.g., from portion 1 to portion 75, to be scrolledwithin the viewing window of submenu 880 and selected by, e.g., tappingthe desired portion. Side menu 870 items Blackout 873 and Exit 874respectively activate functions similar to blackout and exit tools 823and 824 described above. The menus depicted in FIG. 8 are exemplary.Variations of these menus will be appreciated by one of ordinary skillin the art while remaining within the scope of the invention.

FIG. 9 depicts an exemplary view of a user interface on a wirelesshandheld client device 950, displaying information and presentationviews of a conference in accordance with one embodiment. Client device950 includes screen 955 and may be, e.g., an iPhone or iPad provided byApple, Inc. of Cupertino, California. Audience support service 180provides a configurable view of a series of multimedia presentations inconnection with a conference event. Conference window 905 identifiesthree tracks (a track typically relates to a certain subject area, e.g.,CRM), here, Tracks 1-3 correspond to “CRM,” “Financials,” and“Campaigns.” One or more tracks may run in parallel within a conference,e.g., overlapping or concurrently. Within each track is a series ofpresentations, and within each presentation, slides. More generally, aslide is a portion of a multimedia presentation. Presentations appear inpresentation order, thus, Presentation 1 occurs before presentation 2,and so forth. A conference or track “owner” may vary the order ofpresentations as will be described below with respect to FIG. 11.

A user may swipe 960 right or left to respectively open or closeconference window 905. A first visual component in window 917 depicts abar chart, “Slide 7,” of Presentation 4 of Track 1 (CRM). Four smallerwindows 913-916 display thumbnails indicating respectively slides 3-6 ofPresentation 4. A user may touch any of windows 913-916 to view thecorresponding slide in window 917 on demand. Typically, audience supportservice 180 displays only slides that have already been presented,however, this is not limiting and any slides within a presentation maybe displayed. In other embodiments, more or fewer than four thumbnailwindows are displayed on screen 955. A second visual component in window935 depicts a pie chart, “Slide 5,” of Presentation 1 of Track 3(Campaigns). Windows 917 and 935 overlap in a “picture in picture”(“PIP”) arrangement. Here, window 935 is depicted smaller than andoverlapping window 917. Audience support service 180 responds to a usertouching window 935 by swapping (“toggling”) first and second visualcomponents between windows 917 and 935 such that “Slide 7,” originallyappearing in window 917, appears in window 935, and “Slide 5,”originally appearing in window 935, appears in window 917. A secondtouch to window 935 toggles the positions again. A user may view anyslide or presentation merely by touching the appropriate slide orpresentation entry in conference window 905. Touching an entrycorresponding to a presentation, e.g., Presentation 4 of Track 1 (CRM),displays slide one of that presentation by default. Touching a slidewithin a presentation, e.g., Slide 7 of Presentation 4 of Track 1 (CRM),displays the slide, e.g., Slide 7, as depicted in FIG. 9.

FIG. 10 depicts an exemplary view of a user interface on a wirelesshandheld client device 1050, displaying information and presentationviews of a conference in accordance with another embodiment. Certainitems identified by reference numerals in FIG. 10 referring to similarelements in FIG. 9, e.g., screen 1050 of FIG. 10 to screen 950 of FIG.9, were described with respect to FIG. 9 and are omitted here forbrevity. Windows 1017 and 1035 appear in a non-overlapping “pictureoutside of picture” (“POP”) arrangement. Although windows 1017 and 1035are depicted to be approximately the same size, any size relationshipbetween the two windows is arbitrary. Three thumbnail windows 1014-1016appear below window 1017, and function in the same was as described withrespect to windows 913-916. Thumbnail windows 1032-1034 functionsimilarly with respect to window 1035.

FIG. 11 depicts a view of an exemplary data structure for implementing amaster conference in accordance with one embodiment. A conference mayinclude a number of areas of distinct interest (“tracks”), or “paralleltracks,” to audience members. One or more multimedia presentations maybe presented within a track. Parallel tracks may overlap in time. Forexample, a first track might focus on Consumer Relationship Management(“CRM”). A first presentation within the first track might explorebenefits of using CRM, and a second presentation might explain aspecific CRM feature such as lead scoring. A third presentation mightexplain CRM database maintenance, and so forth. A second track, whichmay overlap in time relative to track 1, might focus on financialreporting tools, and contain a plurality of multimedia presentationsspecifically addressing subtopics. As the number of tracks andpresentations grows, organizing and maintaining a multi-track,multi-presentation conference, and notifying conference attendees(audience members), presenters, and related support staff of last minutechanges in scheduling and presentation order, can become challenging.

A master conference provides a way to organize and maintain continuitywithin a conference across a plurality of tracks and multimediapresentations. Data structure 1100 depicted in FIG. 11 is used bydocument management service 175 to coordinate presentations in severaltracks. Data structure 1100 includes a plurality of tables that areexpandable, thus, it supports an arbitrary number of tracks,presentations, users, user keys, and roles. Logically, a masterconference may be thought of as a container holding constituent parts ofthe conference, including, e.g., tracks, presentations, and associationsrelating to scheduling and user access.

Document service 175 determines whether a user has access at thecontainer level—the master conference as a whole—or to a lower level,e.g., portions of the conference, including tracks and presentations.Document service 175 references access tables, for example 1101(master), 1107 and 1108 (track), and 1112 (presentation) in accordancewith one embodiment, to determine what role, if any, a user attemptingaccess to the conference may have. As depicted in FIG. 11, access tables1101, 1107, 1108, and 1112 are set forth individually to facilitateunderstanding. Access data are located in a single access table inaccordance with another embodiment, and may include one or moreadditional columns specifying tracks and presentations associated with auser.

Roles may be numerous and are not limited to those depicted in FIG. 11.For clarity of description, four roles are described with respect toFIG. 11. An “Audience” role grants a user access to view presentations.A “POwner” (presentation owner) role grants a user control over aspecific presentation. The “POwner” may, e.g., view, copy, modify, add,delete, name, re-name, and present a presentation. The “POwner” may alsogenerate a Trailer (see description above), and may associate a trailerwith a presentation by, e.g., scheduling it to appear before thepresentation. For example, “Trailer 1” could have been inserted in row 1of table 1115 above Presentation 1 of Track 2 by a user having a“POwner” role with respect to that presentation. Similarly, the “POwner”may insert an intermission presentation, e.g., a delimiter slide oranother trailer, after the presentation, e.g., “Intermission 1” depictedat table 1115, row 3, following “Presentation 1.” The “POwner” role issuperior to and includes all aspects of the “Audience” role.

A “TOwner” (track owner) role grants a user control over a specifictrack. The “TOwner” may, e.g., view, copy, modify, add, delete, name,re-name, schedule, re-schedule, order, re-order, presentations, and mayschedule, re-schedule, re-order presentations. The “TOwner” role issuperior to and includes all aspects of the “Audience” and “POwner”roles. A “Master” role grants a user container-level access, in otherwords, to the master conference as a whole. A “Master” has full controlover all aspects of the master conference. For example, a “Master” mayview, copy, modify, add, delete, name, re-name, schedule, re-schedule,order, re-order, tracks and presentations, and may schedule,re-schedule, re-order tracks and presentations. A “Master” may also,e.g., modify access tables and related data. The “Master” role issuperior to and includes all aspects of the “TOwner,” “POwner,” and“Audience” roles.

Returning to master access table 1101, it identifies two master users inone embodiment, “Master 1” and “Master 2,” corresponding keys(passwords) “Mas Key 1” and “Mas Key 2,” and corresponding roles,“Master.” Users “Master 1” and “Master 2” therefore have completecontrol (dominion) over the master conference. User names are notlimited to those depicted here, “Master 1” and “Master 2,” and may bearbitrary and in any form, e.g., BigDog, user001@gmail.com, andSid@zohoshow.com. In one embodiment, document service 175 receives auser name and a key, e.g., “Master 1” and “Mas Key 1,” authenticates theuser, and determines with reference to table 1101 that “Master 1” has a“Master” role, entitling it to access the conference as a whole. Master1 may therefore, e.g., schedule and reorder tracks and presentations,modify presentations, and add and remove users.

Presentation tables 1110 and 1115 are respectively associated with rows1 and 2 of a track table 1105 (described below), corresponding to Tracks1 and 2 of the master conference. Tables 1110 and 1115 definepresentation ordering (column 1), display titling (column 2), referenceto user access tables (column 3), reference to a presentation, e.g.,live stream via URL (column 4), define a presentation date and startingtime (column 5), and define a “lockout” period (column 6). Presentation1 is indicated in table 1110 at row 1, column 1. Column 2 specifies itsdisplay title is “Benefits.” Document service 175, via audience supportservice 180, may display “Benefits” from column 2, and other displaytitles identified in tables 1105 (“CRM,” “Financials,” “Campaigns,” 1110(“Benefits,” “Lead Scoring,” “DB maint”, and 1115 (“Overview,” “Basicopns”) in, e.g., conference windows 905 and 1005 respectively ofwireless handheld audience devices 950 and 1050. Column 3 “Access 4”references user access table 1112 (access tables corresponding to Access5-9 are omitted for clarity), and column 4 references a location fromwhich to retrieve Presentation 1, e.g., via URL, http://zhs.com/t1p1.

The URL references a live stream during Presentation 1, and a recordedstream or file afterward in accordance with one embodiment. Column 5specifies an estimated start time for Presentation 1 in YYMMDDHHMMformat. As one of skill in the art may readily comprehend, any formatspecifying a start time may be used. The value in table 1110corresponding to Presentation 1 is “1505200900,” meaning May 20, 2015,9:00 am. Column 6 specifies a lockout period. The lockout featureprevents a user having a superior role to “POwner” from modifying apresentation (here, Presentation 1) after the lockout period begins.This advantageously avoids surprising a presenter, e.g., presenter 155,with last minute changes by a well-meaning but perhaps distant masterconference or track owner—or—by an automated process having the means tomake real-time updates to a presentation prior to its instantiation,e.g., responsive to a customer data resource. The lockout period isspecified in minutes in one embodiment. It is immediately adjacent tothe estimated starting time of a presentation, e.g., the starting timeof Presentation 1 specified in column 5 of table 1110.

For example, document 175 receives a request to modify Presentation 1.The request includes a user identity. Document 175 examines all rolesrelating to the user by referencing, e.g., access tables 1101, 1107,1108, and 1112. If document service 175 determines the user identityincludes a “POwner” role relating to Presentation 1, it moves forwardwith the modification. If document service 175 determines the rolerelating to Presentation 1 is a superior role to “POwner” relating toPresentation 1, e.g., “TOwner” of Track 1 or “Master,” it subtracts thevalue in column 6 (60) from column 5 (1505200900), resulting in alockout time that begins at 1505200800 (May 20, 2015, 8:00 am). It nextreads current time from a real time clock (assumed always available viaAPI or real time computer clock) and compares it to the lockout time. Ifthe current time, e.g., 8:05 am, is later than the lockout time,document service 175 refuses to modify Presentation 1. If current time,e.g., 7:55 am is earlier than the lockout time, document service 175proceeds to allow modification of Presentation 1. Notably, a user may beassociated with a process, thereby enabling the lockout period relatingto automated revisions to a presentation. For example, metadata service490 may be applying modifications to, e.g., Presentation 1 in responsiveto changes in audience composition via customer data service 194. Thelockout period, applied to that service, would prevent real-time changesto the presentation after the lockout period begins. Notably, however,if it is desired for an automated process to work on a presentation inreal time, the lockout period may be avoided simply by assigning theprocess a “POwner” role rather than a superior role.

A track table 1105 defines tracks in three columns identifyingrespectively a track, reference to a user access table, and a displayname. Table 1105 depicts three parallel presentation tracks in column 1,“Track 1” through “Track 3,” and corresponding display names in column3, “CRM,” “Financials,” and “Campaigns.” Column 2, referring to accesstables, e.g., “Access 1,” refers to table 1107, and “Access 2” refers totable 1108. (an access table corresponding to Access 3 is omitted forclarity) Document service 175 receives a user name and key, e.g., “Trk 1own” and “Own Key 1,” authenticates the user, and determines withreference to table 1107 at row 5 that “Trk 1 own” has role “TOwner.”User “Trk 1 own” is therefore a track owner, specifically, of Track 1.Document service 175 will act on instructions it receives from a userhaving the “TOwner” role, here “Trk 1 own,” to, e.g., schedule,re-schedule, re-order, view, copy, add, delete, rename, and modifypresentations within any owned track, here, Track 1. For example,document service 175 receives instructions to swap the order ofPresentations 1 and 2 in Track 1. In response, it copies the entriesfrom table 1110 at row 1 corresponding to Presentation 1 to a temporarytable (not shown), copies the entries from table 1110 at row 3corresponding to Presentation 2 to row 1, thereby overwriting theentries corresponding to Presentation 1 with those corresponding toPresentation 2, and copies the contents of the temporary table to table1110 at row 3, thereby overwriting the entries corresponding toPresentation 2 with those corresponding to Presentation 1. The swap hasthus been effectuated.

In another aspect, document service 175 receives (via audience supportservice 180 because in this example, authentication involves an audiencemember) a user name and key, e.g., “Mbr 1177” and “Aud Key 4,”authenticates the user, and determines with reference to table 1107 atrow 4 that “Mbr 1177” has role “Audience,” corresponding to an audiencemember. The Audience role enables a user to access (view) one or morepresentations. Because user “Mbr 1177” is authenticated with respect toTrack 1, she may access all presentations within Track 1, therebyadvantageously avoiding the need to separately authenticate for eachpresentation. Similarly, “Mbr 1190,” another audience member,authenticates at the master level in table 1101, and therefore mayaccess (view) all presentations within all tracks.

In yet another aspect, one or more presentations may be accessedindividually. Document service 175 authenticates audience member “Mbr1179.” User “Mbr 1179” appears in row 4 of access table 1108corresponding to Track 2, thereby granting “Mbr 1179” access to allpresentations within Track 2 (Financials). “Mbr 1179” also appears inrow 4 of table 1112 corresponding to Presentation 1 of Track 1 (Benefitsof CRM), thereby granting her viewing privileges to that presentation.Other combinations of tracks and presentations are possible.Accordingly, a conference provider may advantageously price, sell, andenforce tiers corresponding to, e.g., a whole conference, one or moretracks, and one or more individual presentations, in any arbitrarycombination.

After a presentation is done, data and information relating to thepresentation, e.g., customer data, any data not yet automatically storedas described above with respect to FIG. 1, are stored to, e.g., CRM. Apresentation may be identified or declared to be “done” in a variety ofways. For example, upon reaching the final slide of, e.g., Presentation1 (Benefits) of Track 1 (CRM), document service 175 displays“Intermission 1,” which it retrieves from in accordance with table 1115,row 3, column 4, and requests customer data service 194 to storeinformation collected during Presentation 1. In another embodiment,presenter support service 178 receives a request from, e.g., presenter155 to end the presentation. In yet another embodiment, document service175 monitors a real time clock and compares it to the estimated startingtime of a subsequent presentation, e.g., Presentation 2 of Track 2. Iftime is running short, e.g., the comparison yields, e.g., 30 minutes(defined in, e.g., a database table) or less, document service 175transmits a request to presenter 155 through presenter support service178 to end the presentation, and ends the presentation upon receiving aresponse from the presenter declaring the presentation to be “done.”

In the foregoing description and in the accompanying drawings, specificterminology and drawing symbols are set forth to provide a thoroughunderstanding of the present invention. In some instances, theterminology and symbols may imply specific details that are not requiredto practice the invention. For example, the wireless handheld devicesdiscussed above are “smart phones” that support many services inaddition to standard voice functions. Portable computing devices otherthan smart phones, such as tablet computers, e.g., an iPad manufacturedby Apple, Inc. of Cupertino, California, and palm-top and lap-topcomputers, can be equipped as detailed herein to serve as wirelesshandheld devices. Moreover, some components or devices are showndirectly connected to one another while others are shown connected viaintermediate components, or wirelessly, e.g., Wi-Fi, Bluetooth, a publicWAN, e.g., the Internet, or a cellular network. In each instance, themethod of interconnection establishes some desired electrical or logicalcommunication between two or more devices, as will be understood bythose of skill in the art. More generally, the term “network” may referto one or more networks of networks, in other words, one or moreinterconnected networks of various types such that a node, e.g., aclient or server device, communicates via the network with another node.A network may include several types of networks, for example, private orpublic networks, local (LAN) and wide area (WAN) networks, wired,wireless, and cellular networks, and the Internet.

FIG. 12 and the following discussion are intended to provide a brief,general description of a suitable computing environment in which theinvention may be implemented. The foregoing examples are described inthe general context of computer-executable instructions, such as programmodules, executed on client and server computers linked through acommunication network, including the Internet. Generally, programmodules include routines, programs, objects, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. In a distributed computing environment, programmodules may be located in both local and remote memory storage devices,and may be executed by client and server computers.

FIG. 12 depicts a general-purpose computing system 1200 that can serveas a client or a server depending on the program modules and componentsincluded. Those skilled in the art will appreciate that the inventionmay be practiced using other system configurations, including hand-helddevices, multiprocessor systems, microprocessor-based or programmableconsumer electronics, network PCs, minicomputers, mainframe computers,and the like.

Computing system 1200 includes a conventional computer 1220, including aprocessing unit 1221, a system memory 1222, and a system bus 1223 thatcouples various system components including the system memory to theprocessing unit 1221. The system bus 1223 may be any of several types ofbus structures, including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. The system memory includes read only memory (ROM) 1224and random access memory (RAM) 1225. A basic input/output system 1226(BIOS), containing the basic routines that help to transfer informationbetween elements within the computer 1220, such as during start-up, isstored in ROM 1224. The computer 1220 further includes a hard disk drive1227 for reading from and writing to a hard disk, not shown, asolid-state drive 1228 (e.g. NAND flash memory), and an optical diskdrive 1230 for reading from or writing to an optical disk 1231 (e.g., aCD or DVD). The hard disk drive 1227 and optical disk drive 1230 areconnected to the system bus 1223 by a hard disk drive interface 1232 andan optical drive interface 1234, respectively. The drives and theirassociated computer-readable media provide nonvolatile storage ofcomputer readable instructions, data structures, program modules andother data for computer 1220. Other types of computer-readable media canbe used.

A number of program modules may be stored on the hard disk, solid statedisk 1228, optical disk 1231, ROM 1224 or RAM 1225, including anoperating system 1235, one or more application programs 1236, otherprogram modules 1237, and program data 1238. A user may enter commandsand information into the computer 1220 through input devices such as akeyboard 1240 and pointing device 1242. Other input devices (not shown)may include a microphone, joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 1221 through a serial port interface 1246 that iscoupled to the system bus, but may be connected by other interfaces,such as a parallel port, game port or a universal serial bus (USB). Amonitor 1247 or other type of display device is also connected to thesystem bus 1223 via an interface, such as a video adapter 1248. Inaddition to the monitor, computers can include or be connected to otherperipheral devices (not shown), such as speakers and printers.

The computer 1220 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer1249. The remote computer 1249 may be another computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the computer 1220, although only a memory storage device 1250 hasbeen illustrated in FIG. 12. The logical connections depicted in FIG. 12include a network connection 1251, which can support a local areanetwork (LAN) and/or a wide area network (WAN). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets and the Internet.

Computer 1220 includes a network interface 1253 to communicate withremote computer 1249 via network connection 1251. In a networkedenvironment, program modules depicted relative to the computer 1220, orportions thereof, may be stored in the remote memory storage device. Itwill be appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computersmay be used.

Presentation Server 165 and Data Server 185 may be realized as one ormore servers, each including one or more services shown withinPresentation Server 165 and Data Server 185, e.g., services 175, 178,180, 183, and 194. Presentation Server 165 and Data Server 185 may alsobe implemented as discrete servers in which each includes a processor,memory, storage, and modules, self-contained within a server havingdiscrete physical boundaries. In this embodiment, communications amongthe processor, memory, storage, and modules, occur internally. Adiscrete server may also be embodied virtually, e.g., via VMWARE, orVIRTUALBOX. Presentation Server 165 and Data Server 185 may also beimplemented in a distributed fashion, e.g., via a “hypervisor”implementation such as VMWARE, or as individual “cloud” services, inwhich processor, memory, and storage are not necessarily physicallyco-extensive. For example, processors 173 and 193 may be distributedacross several physical processors communicating over a local areanetwork. In such implementations, memories 170 and 190 may be physicallyseparate from processors 173 and 193, and storages 184 and 195, andcommunicate over one or more network links. In one embodiment, a networklink is potentially insecure. Some embodiments may therefore supportsecure links and data encryption for the communications into and out ofPresentation Server 165 and Data Server 185. The components of servers165 and 185 may be distributed across local and wide-area networks,including the Internet, as will be readily understood by those ofordinary skill in the art.

Methods and apparatus for enhancing multimedia presentations have beendescribed. In the above description, for purposes of explanation,numerous specific details were set forth. It will be apparent, however,that the disclosed technologies can be practiced without these specificdetails. In other instances, structures and devices are shown in blockdiagram form. For example, the disclosed technologies are described insome implementations with reference to user interfaces and particularhardware. Moreover, the technologies are disclosed above primarily inthe context of multimedia presentations; however, the disclosedtechnologies apply to other data sources and other data types (e.g.,collections of other resources, images, audio, web pages, etc.).

Reference in the specification to “some embodiments,” “someimplementations,” “an embodiment,” or “an implementation” means that aparticular feature, structure, or characteristic described in connectionwith the embodiment or implementation is included in at least someembodiments or implementations of the disclosed technologies. Theappearances of the phrase “in some embodiments,” “in anotherembodiment,” “in some implementations,” or “in another implementation”in various places in the specification are not necessarily all referringto the same implementation or embodiment.

Some portions of the detailed descriptions above were presented in termsof processes or methods and symbolic representations of operations ondata bits within a computer memory. A process or method can generally beconsidered a self-consistent sequence of steps leading to a result. Thesteps may involve physical manipulations of physical quantities. Thesequantities take the form of electrical or magnetic signals capable ofbeing stored, transferred, combined, compared, and otherwisemanipulated. These signals may be referred to as being in the form ofbits, values, elements, symbols, characters, terms, numbers, or thelike.

These and similar terms can be associated with the appropriate physicalquantities and can be considered labels applied to these quantities.Unless specifically stated otherwise as apparent from the priordiscussion, it is appreciated that throughout the description,discussions utilizing terms, for example, “processing” or “computing” or“calculating” or “determining” or “displaying” or the like, may refer tothe action and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission, or display devices.

The disclosed technologies may also relate to an apparatus forperforming the operations or methods herein. This apparatus may bespecially constructed for the required purposes, or it may include ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a computer readable storage medium, for example, any type ofdisk including floppy disks, optical disks, CD ROMs, and magnetic disks,read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, flash memories including USB keyswith non-volatile memory, or any type of non-transitory media suitablefor storing electronic instructions, each coupled to a computer systembus.

The disclosed technologies can take the form of an entirely hardwareimplementation, an entirely software implementation or an implementationcontaining both hardware and software elements. In some implementations,the technology is implemented in software, which includes but is notlimited to firmware, resident software, microcode, etc.

Furthermore, the disclosed technologies can take the form of a computerprogram product accessible from a computer-usable or computer-readablemedium providing program code for use by or in connection with acomputer or any instruction execution system. For the purposes of thisdescription, a computer-usable or computer-readable medium can be anyapparatus that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modems, and Ethernet cards are just a few of thecurrently available types of network adapters.

Finally, the processes, methods, and displays presented herein may notbe inherently related to any particular computer or other apparatus.Various general-purpose systems may be used with programs in accordancewith the teachings herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. The requiredstructure for a variety of these systems will appear from thedescriptions herein. In addition, the disclosed technologies were notdescribed with reference to any particular programming language. It willbe appreciated that a variety of programming languages may be used toimplement the teachings of the technologies as described herein.

The foregoing description of the implementations and embodiments of thepresent techniques and technologies has been presented for purposes ofillustration and description. It is not intended to be exhaustive or tolimit the present techniques and technologies to the precise formdisclosed. Many modifications and variations are possible in light ofthe above teaching. It is intended that the scope of the presenttechniques and technologies be limited not by this detailed description.The present techniques and technologies may be embodied in otherspecific forms without departing from the spirit or essentialcharacteristics thereof. Likewise, the particular naming and division ofthe modules, routines, features, attributes, methodologies, and otheraspects are not mandatory or significant, and the mechanisms thatimplement the present techniques and technologies or its features mayhave different names, divisions, and/or formats. Furthermore, themodules, routines, features, attributes, methodologies, and otheraspects of the present disclosure can be implemented as software,hardware, firmware, or any combination of the three. Also, wherever acomponent, an example of which is a module, is implemented as software,the component can be implemented as a standalone program, as part of alarger program, as a plurality of separate programs, as a statically ordynamically linked library, as a kernel loadable module, as a devicedriver, and/or in every and any other way known now or in the future tothose of ordinary skill in the art of computer programming.Additionally, the present techniques and technologies are in no waylimited to implementation in any specific programming language, or forany specific operating system or environment. Accordingly, thedisclosure of the present techniques and technologies is intended to beillustrative, and not limiting.

Variations of these embodiments, including embodiments in which featuresare used separately or in any combination, will be obvious to those ofordinary skill in the art. Therefore, the spirit and scope of theappended claims should not be limited to the foregoing description. InU.S. applications, only those claims specifically reciting “means for”or “step for” should be construed in the manner required under 35 U.S.C.§112(f).

What is claimed is:
 1. A computer-implemented method for automaticallycreating a multimedia presentation, the computer-implemented methodcomprising: receiving a request to create a first multimediapresentation, the request identifying selection criteria and one or morepre-existing multimedia presentations including a first pre-existingmultimedia presentation; receiving, via a network, first customer datacorresponding to the selection criteria; responsive to the firstcustomer data, selecting a first portion from the first pre-existingmultimedia presentation; and storing and associating the first portionwith the first multimedia presentation.
 2. The computer-implementedmethod of claim 1, wherein the first customer data includes data from athird party.
 3. The computer-implemented method of claim 1, furthercomprising, responsive to the first customer data, selecting a secondportion of the first pre-existing multimedia presentation, and storingand associating the second portion with the first multimediapresentation.
 4. The computer-implemented method of claim 1, wherein thefirst customer data includes a tag.
 5. The computer-implemented methodof claim 1, wherein the first multimedia presentation is tailored to atleast one potential attendee in relation to customer data.
 6. Thecomputer-implemented method of claim 5, further comprising providing tothe at least one potential attendee, a URL to the first multimediapresentation.
 7. The computer-implemented method of claim 5, furthercomprising providing an audience interface to a wireless handheldaudience device via the network, and receiving feedback via the audienceinterface corresponding to the first multimedia presentation.
 8. Thecomputer-implemented method of claim 7, further comprising providing apresenter interface to a presenter device via the network, and sendingthe feedback to the presenter interface.
 9. The computer-implementedmethod of claim 1, further comprising providing a presentation interfaceto a presentation device via the network, directing the first multimediapresentation to the presentation device via the presentation interface,and running the first multimedia presentation in a loop.
 10. Thecomputer-implemented method of claim 1, further comprising receiving,via the network, second customer data, and responsive to the secondcustomer data, updating the first multimedia presentation.
 11. Thecomputer-implemented method of claim 10, wherein the second customerdata is an update corresponding to the first customer data.
 12. Thecomputer-implemented method of claim 10, wherein the receiving thesecond customer data via the network is responsive to making a query viathe network.
 13. The computer-implemented method of claim 1, furthercomprising providing a presenter interface to a wireless handheldpresenter device, and wherein receiving the request to create a firstmultimedia presentation is from the presenter interface.
 14. Acomputer-implemented method for automatically creating a multimediapresentation, the computer-implemented method comprising: receiving arequest to create a first multimedia presentation, the requestspecifying portions, including at least one portion, of one or morepre-existing multimedia presentations; selecting the at least oneportion from the one or more pre-existing multimedia presentations;storing and associating the at least one portion with the firstmultimedia presentation; receiving, from a network, first customer datacorresponding to each portion; and determining a portion duration foreach portion.
 15. The computer-implemented method of claim 14, whereindetermining the portion duration for each portion further comprisesdetermining a relevance of subject matter for each portion based on thefirst customer data corresponding to the portion and relating to apotential attendee, and determining the portion duration responsive tothe relevance of subject matter for each portion.
 16. Thecomputer-implemented method of claim 14, further comprising running thefirst multimedia presentation in a loop.
 17. The computer-implementedmethod of claim 14, wherein the first customer data includes data from athird party.
 18. The computer-implemented method of claim 14, whereinthe first customer data includes a tag.
 19. A computer-implementedsystem for automatically creating a multimedia presentation, thecomputer-implemented system comprising: a processor; a networkinterface; a memory holding data tables and instructions for executionby the processor, the instructions comprising services configured toperform operations including: receiving data from the network interface,managing the data tables and aspects of metadata relating to themultimedia presentation; receiving a request to create a firstmultimedia presentation, the request identifying selection criteria andone or more pre-existing multimedia presentations including a firstpre-existing multimedia presentation; receiving, via the networkinterface, first customer data corresponding to the selection criteria;responsive to the first customer data, selecting a first portion fromthe first pre-existing multimedia presentation; and storing andassociating the first portion with the first multimedia presentation.